Kicksecure Default Browser - Development Considerations

Kicksecure ™

Download

On Computer USB Installation Debian morph to Kicksecure Windows (VM) Linux (VM) Mac (VM) VirtualBox (VM) KVM (VM) Qubes (VM) More options Source Code

About

Overview Features Why Open Source? Project Activities Contributors Mission & Vision

Docs

Documentation FAQ Troubleshooting

Community

Forums Contribute

Support

Self Support First Policy Search Engines, Docs and AI Support (Limited) Reporting Bugs Contact (Restricted)

Tools Upload file Special pages Recent changes Print Version Page meta What links here Related changes Page information

Page Read Edit History Move Protection Unwatch Watch Delete Purge

User Preferences Watchlist Contributions Logout Create account Login

Donate

Exploring the ideal default browser for Kicksecure with a focus on security and privacy, Firefox vs Chromium, browser hardening, considering user freedom, maintainability, security, privacy, no phone home.

Kicksecure Default Browser Considerations

Introduction

Kicksecure is primarily a security focused Linux distribution. Preferring security over privacy if such a decision is unavoidable. However, Kicksecure will never implement outrageous privacy violations. It will even provide slightly better privacy than most other Linux distributions (such as no popularity contest installed), but otherwise no huge efforts to optimize privacy such as in Whonix^®. (And yet, Kicksecure would be a suitable host for Kicksecure until Whonix-Host materializes. No contradiction here since Kicksecure works fine on top of any secure Linux distribution that does not implement outrageous privacy violations.) See also Privacy Goals and Non-Goals of Kicksecure.

Chromium might be more secure than Firefox. Therefore would be the natural choice as default browser for Kicksecure.

very hard to notice Phishing Scam - Firefox / Tor Browser URL not showing real Domain Name - Homograph attack (Punycode)

Even if Firefox would provide better privacy than Chromium, this would still not speak in favor of choosing Firefox as the only browser installed by default in Kicksecure because as elaborated in the first paragraph in this chapter, Kicksecure is primarily a security focused Linux distribution.

Other browsers not available from packages.debian.org are not considered (at least not in initial versions) because Kicksecure will have a default application policy similar to Whonix default application policy .

However, Firefox should be preferred for reasons other than security and privacy, see threats to user freedom through market share domination. In future, Firefox might have better advertising blocking capabilities?

See also these Chromium considerations.

Therefore the decision which browser to install by default in Kicksecure is a difficult one.

To not let the perfect be the enemy of the good,

Nowadays Firefox is installed by default due to Chromium Debian Package Security Issues.

The decision is based on practicality, available resources, achievable initial goals. It is a significant development effort to create a dedicated website for Kicksecure and to create a new Linux distribution. Kicksecure doesn't have to find solutions to the difficult mostly globally unaddressed Miscellaneous Threats to User Freedom right from the start.

See also #Potential Future Solutions which might be implemented in later stages of the development.

Disregarded Solutions

no browser installed by default

• That would be a terrible user experience, specifically for Live ISO / USB users, waiting until all browser related packages are downloaded and installed using APT. Users want ready to go solution. The fact that they already have to invest time to get a new operating system is already a barrier. Asking them to wait till a browser downloads is too much.

install both firefox-esr and chromium by default

• a waste of disk space
• longer update times as both packages are downloaded in the future
• not a strong stance against chromium

Potential Future Solutions

Might be implemented in a later version but not in the initial versions.

Browser Choice Dialog

Similar to this:

https://upload.wikimedia.org/wikipedia/en/e/e2/BrowserChoice.gif

During the build process of Kicksecure download (cache) both packages, firefox-esr and chromium but don't install these. This is to avoid APT traffic and time wasted on network download. In more technical terms, similar to this:

sudo apt update
sudo apt install --download-only firefox-esr
sudo apt install --download-only chromium

The packages will then be cached but didn't actually install the packages. These downloaded packages files will reside in folder /var/cache/apt/archives and otherwise do nothing. Would be cleaned up once the user runs sudo apt clean.

That would work well for ISO release but not for installation from repository. The latter not sure how important long term, perhaps for servers (server vendors won't offer Kicksecure pre-install very soon) but then for servers no browser is required.

Not sure yet this can work with the ISO build process.

Also after first boot there is a technical issue. Suppose users would run sudo apt update followed by sudo apt full-upgrade before ever starting a browser, which is recommended and good security practice. Then when running the browser choice dialog (through clicking browser icon in start menu)...

At this point the user most likely the browser choice tool cannot run sudo apt install firefox-esr or sudo apt install chromium on behalf of the user without network traffic. This is because dependencies, package versions changed meanwhile. (User run sudo apt update would have noticed that.) This decreases usability. Thereby the browser choice tool would be changed from offline install previously downloaded browser package to network dependent download and install of browser.

To keep the browser choice tool offline install previously downloaded browser package should the browser choice be a popup at first boot?

There might be technical solutions for all of this but this makes the default browser choice a major development task.

draft text for browser choice dialog

Not relevant yet since the browser choice dialog will not be implemented soon.

Kicksecure supports any Debian compatible browser, but defaults to two major choices: Chromium and Firefox.

• Firefox - Pros: Keeps the web open and free as we know it. Less secure.

• Chromium - Pros: More secure. Cons: Increases Google's influence, which may harm user freedom and choice in the future.

Please make a selection:

[x] Firefox
[ ] Chromium
[ ] Do not install any browser at this time
[ ] Do not ask again
[ ] Quit

Domain name will change to kicksecure.com.

Comparison of Browsers

Original Firefox

https://www.kuketz-blog.de/firefox-datenschutzverstoss-bei-der-android-version/

Trademark Disclaimer: Kicksecure is not officially associated with Mozilla Firefox. See Disclaimer.

advantages:

keeping the firefox branding and improving upon it might be more user friendly than shipping unpopular brand browsers.https://github.com/Kicksecure/security-misc/issues/192#issuecomment-1910675642

issues:

• trademark issues:
  • With Debian: Past trademark nonsense by Mozilla, see Debian–Mozilla trademark dispute. Was resolved and hopefully will not happen again.
  • With LibreFox: What happened? See LibreFox.
  • Future: Firefox Potential Legal Risk

disadvantages:

• Promotes non-freedom software: Easily downloads the non-freedom DRM plugin from Google. Related: avoid non-freedom software
  • https://support.mozilla.org/en-US/kb/enable-drm
  • DRM test website: https://bitmovin.com/demos/drm
• Needs hardening: Not as hardened by default (lower attack surface, disabled telemetry) as it could be creating demand for a hardened Firefox fork or Firefox settings project such as arkenfox.

Enabling non-freedom DRM is just 1 click away:

You must enable DRM to play some audio or video on this page. Learn more [Enable DRM]Firefox when visiting a DRM test website

TODO:

• As part of taming Firefox, a Firefox settings project such as arkenfox or Firefox might make it harder to accidentally enable DRM?

Firefox directly from Upstream Mozilla using Flatpak

advantages:

• Fast stable Firefox upgrades directly from upstream, Mozilla.

issues:

• Most likely ignores /etc/firefox settings folder. It is most likely possible to add a workaround for that.

See also:

• Flatpak

Firefox directly from Upstream Mozilla using packages.mozilla.org

advantages:

• Fast stable Firefox upgrades directly from upstream, Mozilla.

potential issues:

• TODO: Does it honor /etc/firefox settings folder? It might not as this might only be a feature by Debian's firefox-esr package.

disadvantages:

• Same as in above wiki chapter.
• Foreign Sources

Firefox from packages.debian.org

Also when using Debian's Firefox package, enabling non-freedom software DRM is just 1 click away.

Disclaimer

There are two different entities.

• A) Mozilla: Developer of the Mozilla Firefox browser. Versus,
• B) Kicksecure: An independent Linux distribution.

Kicksecure is not officially associated with Mozilla Firefox. The Mozilla Firefox logo is trademarked by Mozilla.

Why this disclaimer? See Firefox Potential Legal Risk.

Firefox Potential Legal Risk

Background story: Debian–Mozilla trademark dispute (resolved in 2017)

Quote:

= About the Debian specific patches =

Mozilla recognizes that patches applied to Iceweasel/Firefox don't impact the quality of the product. Patches which should be reported upstream to improve the product always have been forward upstream by the Debian packagers. Mozilla agrees about specific patches to facilitate the support of Iceweasel on architecture supported by Debian or Debian-specific patches.

More generally, Mozilla trusts the Debian packagers to use their best judgment to achieve the same quality as the official Firefox binaries.

In case of derivatives of Debian, Firefox branding can be used as long as the patches applied are in the same category as described above. Ubuntu having a different packaging, this does not apply to that

distribution.Debian issue tracker, Renaming Iceweasel to Firefox

Opinion by a non-lawyer:

The phrasing can be used as long as the patches applied are in the same category as described above could be interpreted as in a patch which disables all telemetry, tracking and phone-home as much as possible would be in a different category and hence might in the viewpoint of Mozillla violate their trademark.

Mozilla vs portapps.io from 2019

Following a trademark violation report (#11) from Mozilla, Firefox portable has been named Phyrox portable on Portapps. Nothing changes except its name.phyrox-portable

But even modest changes to preferences (such as whether "Know Your Rights" information is displayed to users) are sufficient to violate our policy against distributing modified versions of Mozilla software with our trademarks. Of course, end-users may choose to change preferences and settings in Firefox. But we don't allow others to distribute unofficial versions of "Firefox" with modified configurations or preferences.phyrox-portable published an e-mail from a Mozilla attorney.

Does this apply to Linux distributions that is not really primarily about distributing Firefox? Probably yes, since Mozilla had also a past conflict with Debian.

Changes requiring Mozilla’s prior written permission include (but are not limited to):

• Changing the default home page or adding bookmarks,Mozilla Trademark Distribution Policy

Potentially also Mozilla vs LibreFox had a trademark conflict.

Correspondence with Mozilla about its Trademark

15 February 2024

From:

adrelanos

To:

trademark-permissions@mozilla.com

subject:

Kicksecure Default Browser Configuration Trademark Question

body:

I am the lead developer of the Kicksecure project, a Linux distribution focused on security and based on Debian. Kicksecure is developed by the same team as Whonix, which is somewhat more well-known.

Our hardened defaults extend to the default user applications on the system, including a daily drivable web browser.

We are currently in the process of reviewing and considering potential candidates to be the default web browser on Kicksecure.

With good intentions, various Kicksecure contributors have suggested shipping Mozilla Firefox as the default browser. However, some contributors, including myself, are concerned about the modifications to Firefox's default settings we intend to make, versus Mozilla's Trademark Policy. We have no intention of rebranding or changing the compilation options of Firefox binaries. In fact, we prefer to keep the Mozilla trademarked names for the products to provide our users with a sense of familiarity.

We would acquire unaltered binaries from one of the following sources:

- Debian's official packages.debian.org repository
- Mozilla's official packages.mozilla.org repository
- Mozilla's official Firefox Flathub repository

Ideally, we would use Mozilla sources.

Here is a trademark-respecting list of things we are aware of and want to avoid for understandable reasons:

* Not using Mozilla trademarks in the name of our business, product, service, app, domain name, publication, or other offering.
* Not using marks, logos, company names, slogans, domain names, or designs that are confusingly similar to Mozilla trademarks.
* Not using Mozilla trademarks in a way that incorrectly implies affiliation with, or sponsorship, endorsement, or approval by Mozilla of our products or services.
* Not displaying Mozilla trademarks more prominently than our product, service, or company name.
* Not using Mozilla trademarks on merchandise for sale (e.g., selling t-shirts, mugs, etc.)
* Not using Mozilla trademarks for any other form of commercial use (e.g., offering technical support services), unless such use is limited to a truthful and descriptive reference (e.g., “Independent technical support for Mozilla’s Firefox browser”).
* Not modifying Mozilla’s trademarks, abbreviating them, or combining them with any other symbols, words, or images, or incorporating them into a tagline or slogan.

And here is a list of things that we would like to do. Our primary intention is to have a default policy (or employ other means if more appropriate) to do the following:

* Use unaltered binaries.
* Disable all Telemetry, Studies, Reports, and non-essential implicit outgoing connections.
* Force install the addon "uBlock Origin" by Raymond Hill.
* Set and lock hardened SSL/TLS-related settings, including, but not limited to, setting HTTPS-only mode as the default, blocking mixed content, not trusting unsafe negotiations, disabling unencrypted background requests, etc.
* Disable sponsored components, like bookmarks and suggestions.
* Set and lock strict mode for ETP.
* Change the default homepage.
* Disable the default display of the "Know Your Rights" information page.

As an illustrative point of how specifically we plan to apply these changes:

- Our intended changes would be made by providing a separate package (for example, named "hardened-browser-config").
- This package would install config file(s) in folder(s) such as /etc/firefox or /etc/firefox-esr.
- The package would be installed by default.

We are willing to elaborate on the details and consider making modifications upon request by Mozilla.

We are not asking for any special permission that does not extend to derivatives. As stated on the Debian issue tracker:

> In case of derivatives of Debian, Firefox branding can be used as long
> as the patches applied are in the same category as described above.

This is related to the Debian Free Software Guidelines (DFSG) (item 8):

> License must not be specific to Debian
>
> The rights attached to the program must not depend on the program's being part of a Debian system. If the program is extracted from Debian and used or distributed without Debian but otherwise within the terms of the program's license, all parties to whom the program is redistributed should have the same rights as those that are granted in conjunction with the Debian system.

We would like to be able to state similarly:

> In case of derivatives of Kicksecure, Firefox branding can be used as long as the patches applied are in the same category as described above.

We are asking for your opinion on whether this would be in conflict with Mozilla's Trademark Policy.

We intend to publish our correspondence for the sake of transparency. Our communications and your responses will be publicized in full, verbatim, without modifications.

06 March 2024

Patrick,

Thanks for your email.

Unfortunately the changes you would like to make do not comply with our
distribution policy
<https://www.mozilla.org/foundation/trademarks/distribution-policy/>,
including the following:

You may not add to, remove, or change any part of the software, including
the Mozilla trademarks themselves. For example, you may not add any
extensions to Firefox, change default settings, or alter search codes.

If you would like to distribute Firefox unmodified, you can use our .deb.

You can, of course, make any modifications you wish to Firefox’s open
source software if you distribute a browser without Mozilla and Firefox
trademarks. Based on your requirements, the Tor Browser might also be an
option you could consider.

Mike Kaply
Technical Partner Lead
Mozilla Corporation

For the full e-mail including headers see footnote.

arkenfox

https://github.com/arkenfox/user.js

A settings file improving Firefox security and privacy.

todo

advantages:

• disabled telemetry by default

issues:

• Phone home. Does not do anything about Firefox phone home. Feature Request: Radio Silence by Default for Browser Startup and Background Connections aka "Disable Phone Home" got instantly closed, rejected and locked for further discussion.
  • https://github.com/arkenfox/user.js/issues/917 was deleted but is still available on https://web.archive.org/web/20210602135212/https://github.com/arkenfox/user.js/issues/917#issuecomment-609087428
    • also deleted:
      • https://web.archive.org/web/20210602135212/https://github.com/arkenfox/user.js/issues/892
      • https://web.archive.org/web/20210602135212/https://github.com/arkenfox/user.js/issues/893

non-issues:

• https://github.com/arkenfox/user.js/issues/1795
• Telemetry. Ticket https://github.com/arkenfox/user.js/issues/1660 is confusing but it's not about enabling telemetry. Only about moving it to its own section in the config file. Which is more like a textual, stylistic change.
• using pref( instead of user_pref( is not an issue as per https://github.com/Kicksecure/security-misc/pull/183#issuecomment-1895948795

That could easily be handled during the package build process with something like this:

search='pref("'
replace='user_pref("'
file_name='user.js'
str_replace "$search" "$replace" "$file_name"

The diff would be reasonably simple.

deskapps-harden

https://github.com/monsieuremre/deskapps-harden

A settings file improving Firefox security and privacy.

todo:

• discuss if settings locking is really necessary: https://github.com/Kicksecure/security-misc/issues/192#issuecomment-1905981518

advantages:

• responsive upstream
• founded by Kicksecure contributor
• clean, small, policy, single 1 file

disadvantages:

• new project
• few users, bug reports, feature requests yet, hence difficult to judge the merits of the project
• no known third-party reviews yet
• project name might be too limiting to gain lots of non-Kicksecure users using the same, which would be an advantage to get more users (fingerprint shared by more users and hopefully more review, suggestions)

LibreWolf

Lags behind Firefox a few days up to 1 week.

Regarding Librewolf’s slow updates, I think this issue has been very greatly exaggerated, having used it as one of my browsers for almost over 30 months, I personally do not recall it ever really being more than one week behind Firefox, usually it is only a couple working days at worst.https://github.com/Kicksecure/security-misc/issues/192#issuecomment-1910407278

LibreWolf feature request: Radio Silence by Default for Browser Startup and Background Connections aka "Disable Phone Home" #1779

Bugs reported to only be reproducible in LibreWolf but not in Firefox:

• https://codeberg.org/librewolf/issues/issues/1769

Bugs maybe specific to LibreWolf only but not Firefox:

• https://codeberg.org/librewolf/issues/issues/1774

LibreFox

https://github.com/intika/Librefox is dead as per https://github.com/intika/Librefox/issues/141

LibreWolf (https://librewolf-community.gitlab.io/) is active.

LibreFox had a potential legal issue with Mozilla:

• https://github.com/intika/Librefox/commit/45a4d3ce647b8c896e81ce3e5ac5ddc95ff045e0 mentions legal issues.
• question about it: https://github.com/intika/Librefox/issues/125#issuecomment-1913347606

intika, the developer of Librefox disappeared. The website linuxhacks.org is still online so one could assume that someone is still paying the bills. Still active on stackexchange.

Mullvad Browser

Upstream Documentation:

• https://mullvad.net/en/browser
• https://mullvad.net/en/browser/hard-facts

Kicksecure user documentation:

• Opt-in Installation: Users can easily opt-in to install Mullvad Browser (MB).

Advantages:

• Anti-browser fingerprinting: Provides enhanced privacy by preventing tracking through browser fingerprint techniques.
• Company stability: Unlikely to be deprecated, as Mullvad has been established for a significant duration.
• VPN support: Compatible with VPNs, though does not require one by default.
• Security features: Includes a security slider for customizable security settings.
• Software compatibility: Supported by tb-updater and tb-starter, as noted in Kicksecure user documentation.

Disadvantages:

• Vendor branding: Features specific Mullvad branding, therefore not vendor-neutral.
  • Home page and extensions: Includes a default homepage and browser extension specific to Mullvad.

    • MULLVAD BROWSER

    • Developed in collaboration between the Tor Project and Mullvad VPN

    • Disable Mullvad DoH (encrypted DNS)
• Purpose of browser:
  • Opinion: This is interpretation, opinion based.
    • A) Mullvad users: MB's primary purpose is to increase the usefulness of Mullvad's VPN service.
    • B) Advertisement: MB serves as a distinguishing advantage over Mullvad's competitors and an advertisement for Mullvad.
    • C) Non-Mullvad users: Enhanced privacy and security.
• VPN confusion: Users might mistakenly believe that the VPN is active by default. This is addressed in the Mullvad VPN section of the user documentation.
• Browser basis: Based on Firefox ESR (extended support release), not the latest stable version of Firefox.
• DNS configuration:
  • Mullvad Browser default DNS configuration: DNS over HTTPS enabled by default, utilizing Mullvad's services.
  • Privacy implications: Not the DNS server a user or corporate might have configured (such as on the router level) will be used but Mullvad's DNS server. Therefore Mullvad will also learn all DNS queries by the user.
  • Violation of separation of power: For example, the developers of Tor do not host Tor relays. One party is maintaining the software and other parties are maintaining the infrastructure. Similarly, it could be argued browser developers should only maintain the browser but stay neutral regarding network infrastructure.
  • DNS settings inconsistency: This leads to inconsistency with system-wide DNS settings. There would be one set of DNS settings for the system and a different set of settings for Mullvad Browser.
  • Usability: This is a violation of the principle of least astonishment (POLA).
  • Increased DNS Configuration Changes Complexity: Changes to system DNS settings by the user or Kicksecure should apply consistently across the entire system, including the browser. Using separate DNS settings in MB could complicate development of a more secure default system DNS configuration and cause the browser to use different DNS settings than the system default.
  • See also: DNS Security and the forum discussion Use DNSCrypt by default in Kicksecure? (not Whonix).
• Usability:
  • No stored logins: Does not save logins because Mullvad Browser does not save cookies after a browser restart. Therefore, users would have to log in repeatedly.
  • No password manager: Does not come with a password manager by default. Users would need to re-enter their passwords for pages where they intend to use logins repeatedly.

Other:

• uBlock Origin: Pre-installed but not enabled by default.

Packaging Mullvad Browser (MB):

• Future packaging plans: Efforts to release deb/rpm packages are confirmed for this year.

  • Getting deb/rpm package for Mullvad Browser is firmly in the plans for this year.

• MB feature request: Add rpm/deb package repositories?

Related:

• https://forums.kicksecure.com/t/tor-project-is-resurrecting-secbrowser-as-mullvad-browser/101

Mullvad Browser as Kicksecure Default Browser

• Summary: No. This is a declined feature request. Details? See below.
• Comparison with others: No other Linux distribution is installing Mullvad Browser by default. This implies that such a decision needs to be considered with extra care.
  • Qubes: At time of writing, there is no Mullvad Browser related feature request at the Qubes issue tracker.
• Opinion: By Kicksecure founder and developer:
  • Trademark: No trademark policy issues.
  • Not vendor neutral: Unfortunately, Mullvad Browser is not a vendor-neutral browser project as Base Browser might be.
  • Community project vs corporate project: MB is developed by a VPN company and not a community project solely focusing on maintaining an independent web browser.
  • Omnipresent VPN company advertisements: Many or even most podcasts, popular YouTube channels, and so forth contain advertisements for VPN companies. While Mullvad at the time of writing does not seem to sponsor any content creators, it is in the same category as VPN companies, which matters for reputational reasons.
  • VPN review websites: Most VPN review websites and reviews seem to be sponsored by VPN companies. This seems to be a popular opinion.
  • Low Quality and Questionable Morality of VPNs generally: VPNs often come across as low-quality due to their pervasive and morally dubious advertising practices. VPNs don't make you anonymous but are often advertised or perceived as anonymity tools by many users. For examples of that, please follow this link and press expand on the right side. This criticism is general and not directed at Mullvad, which does not seem to engage in such practices.
  • Implied Relationship of VPN Company Sponsoring: If any Linux distribution (such as Kicksecure) would install a browser by default that contains the branding of a VPN company (such as Mullvad Browser), this might lead to users strongly suspecting that the VPN company is paying the Linux distribution for this and as a result might have inappropriate influence over the Linux distributions. This would happen irrespective of whether there actually has been an advertisement deal or not. Disclaimers would only partially help as these might often either not be noticed or regarded as incredible.
  • Reputational impact: Any reputation risk or damage is best avoided. Reputational integrity is deemed to be more foundational for the project's success than any technical advantages that any browser might provide.
  • Actual impact: While the facts (non-existence of a sponsorship deal, no influence by the VPN company on the Linux distribution) are all positive, avoidance of easily confused and negative impressions is best pursued for pragmatic reasons to avoid jeopardizing the overall success of the project.
  • Conclusion: To avoid any confusion, suspicion of having sold out, I have decided not to install any software by default that comes with branding or advertisements from any VPN companies.

Tor Browser

Not an option by default in Kicksecure because it is torified, hence slow. For that use case it would be better to use Whonix. See also Privacy Goals and Non-Goals of Kicksecure.

However, easily installable, opt-in for users of Kicksecure, see Tor Browser.

Tor Browser without Tor

As long as Tor Browser still says "Tor Browser" in the title bar it will be too confusing. Same issue that SecBrowser had. Related: In-House Browser Development

Base Browser

Both, Mullvad Browser (MB) and Tor Browser (TB) are based on Base Browser (BB). However, Base Browser only exists as a source code repository. There are no binary builds available. Base Browser presumably has neither the Mullvad Browser nor Tor Browser branding, which is good. It is not separately maintained as a standalone project by any upstream. Not suitable for the same reasons as documented in chapter Unbranded or Rebranded Browser.

Feature Request Maintain a Standalone "Base Browser" has been rejected.

Unbranded or Rebranded Browser

Unbranded or Rebranded Browser is not a third-party project. It means that the Kicksecure project would take an existing browser such as Mullvad Browser to unbrand or rebrand it.

This is not an option at this time because it is difficult and time-consuming to unbrand, for example, Mullvad Browser, and compile it. The maintenance effort is high and not justified given the current available project resources.

Mozilla Firefox feature request: Add an Unbranding Option in Firefox Settings

related:

• https://wiki.mozilla.org/Add-ons/Extension_Signing#Unbranded_Builds
• In-House Browser Development

In-House Browser Development

Not possible with the current available project resources.

For example, see https://codeberg.org/librewolf/issues/issues to see the flood of complex issues that are constantly coming up.

PureOS previously maintained PureBrowser, but it got deprecated due to the too high maintenance effort.

There seem to be lots projects out there to “unMozilla” Firefox (removing things like DRM, telemetry, Pocket integration, etc) but it’s getting harder to do that with every Firefox release. That’s what we were up against with PureBrowser and it unfortunately became too daunting of a task (even with tracking ESR like we were). We also wanted to release close to upstream so we had the latest security patches ASAP but again, became unfeasible for our small team.https://forums.puri.sm/t/purebrowser-removed-after-update/8635/11

Waterfox

https://www.waterfox.net/

TODO: ?

https://github.com/Kicksecure/security-misc/issues/192#issuecomment-2269688442

Pale Moon

https://www.palemoon.org/

TODO: ?

ffprofile.com

https://ffprofile.com/

https://github.com/allo-/ffprofile

TODO: ?

GNUzilla

• https://www.gnu.org/software/gnuzilla/
• https://directory.fsf.org/wiki/Gnuzilla

TODO: ?

pyllyukko user.js

https://github.com/pyllyukko/user.js

no phone home feature request: https://github.com/pyllyukko/user.js/issues/509#issuecomment-1947855378

More

• https://codeberg.org/rusty-snake/firefox-config
• https://github.com/crssi/Firefox
• https://github.com/yokoffing/Betterfox

TODO: ?

Criteria

Primary importance for Kicksecure must be security. Anti-fingerprinting is nice but secondary. Disabled telemetry can be considered a security feature since it lowers attack surface and a privacy feature. Radio Silence (as defined in LibreWolf feature request Radio Silence by Default for Browser Startup and Background Connections aka "Disable Phone Home" #1779) would be nice to have.

See also Privacy Goals and Non-Goals of Kicksecure.

Conclusion

A lot of presumably more secure by default (and better privacy by default) browsers have been considered.

No suitable, well-maintained with timely security upgrades, vendor-neutral, acceptable usability browser project could be found.

Discussions

• Chromium Browser for Kicksecure Discussions (not Whonix)
• Kicksecure Default Browser Discussion
• https://forum.qubes-os.org/t/is-there-a-reason-firefox-needs-to-have-vulnerable-insecure-settings-in-the-templates/23566
• https://forum.qubes-os.org/t/is-firefox-really-an-appropriate-default-browser-for-qubes/26042

See Also

• https://www.unixsheikh.com/articles/choose-your-browser-carefully.html
  • https://archive.is/lTOFc

Related

• Chrome
• Chromium
• Dev/Chromium
• Dev/Default Browser
• Google Chrome Repository Insecurity
• https://forums.whonix.org/t/chromium-browser-for-kicksecure-discussions-not-whonix/10388

Footnotes

Kicksecure A secure by default operating system with the latest security research in place.

Dark mode

Follow us on social media

Supported by Power Up Privacy

Kicksecure is proudly supported until 2025 by Power Up Privacy, a privacy advocacy group that seeks to supercharge privacy projects with resources so they can complete their mission of making our world a better place. (Strictly subject to our sponsorship policy.)

At Kicksecure we value freedom and trust, supporting Open Source and Freedom Software

By using this website, you acknowledge you have read, understood, and agree to be bound by these agreements: Terms of Service, Privacy Policy, Cookie Policy, E-Sign Consent, DMCA, Imprint 2012- 2024 ENCRYPTED SUPPORT LP

Your support makes
all the difference!

We believe security software like Kicksecure needs to remain Open Source and independent. Would you help sustain and grow the project? Learn more about our 12 year success story and maybe DONATE!