Browser choice

Patrick · September 16, 2025, 5:06am

Does browser choice depend on it or is it separated from it?

browser-choice debian/control file currently Depends: on
tb-updater and tb-starter. Maybe not ideal.

The only caveat is if you like to have multiple Tor Browser instances there is no way to set the folder path to download it to other then .tb folder in home folder in regards to tb-updater.

These variables are all configurable. If that interests you, please
create a separate forum thread for support.

Quiksilver · October 19, 2025, 4:14pm

You guys should see or get in contact with the devs of HydraVeil

Something like that could maybe be added to browser-choice for isolated fingerprints by altering the timezone and resolution using bwrap for browsers.

Noted are there any plans to add check mark options to browser-choice to install things like custom user.js or enterprise policies for included browsers like for example a user.js or policy to make Firefox configured to work with I2P?

Patrick · October 20, 2025, 4:42pm

This is out-of-scope for Kicksecure. As per:

This is also out-of-scope for browser-choice, which offers are selection of browsers based on criteria for inclusion into browser choice, but doesn’t modify browsers.

So for browsers to gain such features, these would need to be implemented in the browser itself.

This might be a suitable feature request for Whonix.

No, as per:

Patrick · January 14, 2026, 8:41am

github.com/Kicksecure/browser-choice

Add a policy option for users who need captive portals on chromium [Feature Request]

opened 04:34PM - 13 Jan 26 UTC

NomadicUser

Despite after making sure my keyring was unlocked (the annoying popup for chrome… browsers) on linux. I was not able to connect to any public WiFi captive portals I tested. This is unrelated to the fact that most places in the US use AT&T as their provider. I looked into this and captive portals are almost always over a http not https. Chromium forces handling of http to upgrade to https and many users report this issue. I proceeded to create a global policy and it fixed the issue for me: ``` { "BasicAuthOverHttpEnabled": true, "HttpsUpgradesEnabled": false } ``` [HttpsUpgradesEnabled](https://chromeenterprise.google/policies/#HttpsUpgradesEnabled) may not need to be set I didn't try without it but BasicAuthOverHttpEnabled most certainly needs to be set to even reach captive portals. Chrome 154 will set [HTTPS by default](https://security.googleblog.com/2025/10/https-by-default.html) which I bet will lead to more people having this issue. Currently though the default chrome settings disallows Basic Authentication dialogs on plain HTTP which almost most public captive portal gateways use. The second is chrome automatically upgrades any `http://` request to `https://` before sending it by default. The global policy directory for all users is `/etc/chromium/policies/managed/` and chrome supports multiple policy files in the directory. > Any JSON files placed there are read and merged together, so you can split your configuration across multiple policy files if that makes management easier. This makes it easy if more such "Enterprise Policy" options were added to browser choice in the future: ``` /etc/chromium/policies/managed/ ├── 01_browser-choice_captive-portal-policy.json └── 02‑homepage‑policy.json ``` ## Summery - Please add a check box option for Brave Browser and Chromium to create a Enterprise policy at install. ``` - **Enterprise Policies:** [ ] Enable access to Captive Portals (Public WiFi) ```

github.com/Kicksecure/browser-choice

Add Brave Browser Onion Repo install/update option

opened 04:19PM - 13 Jan 26 UTC

NomadicUser

Please add an option to the Repo install of Brave to update and install the brow…ser over Brave's Onion `tor+https://brave-browser-apt-release.s3.brave4u7jddbv7cyviptqjc7jusxh72uik7zt6adtckl5f4nwy2v72qd.onion` rather the clear connection. The very least `tor+https://brave-browser-apt-release.s3.brave.com` cause I saw it was not torified over apt after installing and I doubt I'm the only one who would like such a feature. (Kicksecure already updates over Tor) I have been updating the browser over tor for some time but not with the newest debian source format but last I checked the new format supports the tor+ format provided by apt-transport-tor. ``` sudo tee /etc/apt/sources.list.d/brave-browser.list > /dev/null <<'EOF' Types: deb URIs: tor+https://brave-browser-apt-release.s3.brave4u7jddbv7cyviptqjc7jusxh72uik7zt6adtckl5f4nwy2v72qd.onion Suites: stable Components: main Architectures: amd64 arm64 Signed-By: /usr/share/keyrings/brave-browser-archive-keyring.gpg EOF ``` ``` sudo tee /etc/apt/sources.list.d/brave-browser.list > /dev/null <<'EOF' Types: deb URIs: tor+https://brave-browser-apt-release.s3.brave.com Suites: stable Components: main Architectures: amd64 arm64 Signed-By: /usr/share/keyrings/brave-browser-archive-keyring.gpg EOF ``` ### Basic Summery Include checkbox for in the repo option to either update/install over the onion or basic tor+ for users.