1 lien privé
An independent fork of Firefox, with the primary goals of privacy, security and user freedom.
A custom version of Firefox, focused on privacy, security and freedom.
https://librewolf.net/
LibreWolf - Le Firefox blindé pour la vie privée
https://korben.info/librewolf-firefox-blinde-vie-privee-sans-configuration.html
Open-source tests of web browser privacy
https://privacytests.org/
I'd like to start this by saying that 'hardened FF' does not refer to a particular setup but it's a general term that became popular to refer to the use of user.js to improve privacy and security on FF.
No, we do not use the same setup as PTIO. For example we disable trackingprotection in favour of uBlock and we do not use FPI. We share some prefs but the setups are still different.
The same is true for Arkenfox, we include some of their pref but there are also major differences: FPI, Safe Browsing, trackingprotection and many more. These are important differences and you should be aware of them. You can easily see that our .cfg is different from their user.js by the number of included prefs, we have a lot more than they do as we decided to disable basically all of Mozilla stuff, while they do not mind having it in FF so they leave it as it is, and we also remove URLs and keep some redundant stuff, which in arkenfox's view is not ideal as it makes re-enabling stuff harder.
With that being said, as you correctly pointed out, arkenfox is a project that we refer to in order to improve our configuration and this is particularly true at the moment since we are doing a cleanup and general improvement of our settings. We noticed that we need to improve some stuff, remove some outdated prefs, and then have a better way to handle them in the future, and this requires to review the current setup. So I think the proper reply would be: no, our config is not the same as arkenfox despite the fact that we share several prefs, but we look at their project to improve our setup and we want to keep up with it. With that being said LibreWolf has its own configuration with its own choices, which differ from arkenfox.
Regarding the difference with any kind of hardened FF, I think the main one is that we try to be private by default so you don't need to go the extra mile and configure your own user.js and settings, or even longer go through the entire build process to disable some stuff in depth. This means that we disable telemetry, apply our own hardened configuration and we also ship the browser with uBlock by default. Additionally we decide to remove all Mozilla stuff that we catch, as we think it has no reason to be preinstalled on a browser, we include privacy respecting providers by default and we try to disable as many non-user-triggered outgoing connections as possible.
In addition to this, I personally value that LW is community driven and that it tries to be private by default vs configurable for privacy, which is the case for FF+user.js. I also believe in this project as a chance to make a statement on what we consider a proper way to respect users when shipping software. This probably won't mean much to most people using LibreWolf, but I consider these valid reasons for why I use it and contribute to it.