- •
- 7M
- •
back again with another major release (and yes I only post for major releases but every minor firefox release equals to a new librewolf release). osx is out, linux and windows are getting worked on, you can expect them soon.
main changes:
- based on firefox v95.
- there’s an issue (see my comment and the firefox ticket) with the build process that does not allow to successfully compile with the new wasm sandboxing, hence we had to use the “old sandboxing” for now. as soon as an upstream fix is delivered or we find a workaround we will immediately release a new update. edit: FIXED.
- new uBO version.
- updated settings. for more details see the changelog and the reference issues linked in it, but in short:
- larger but still rfp compliant window size, to improve usability.
- webrtc is no longer disabled (but the private IP is still protected so no worries), which should mean less breakage by default.
- the geo API is no longer disabled as it can be fingerprinted and location aware browsing is behind a per-site and per-session prompt.
- in this release you shouldn’t experience logouts when allowing exceptions.
- rfp dark mode override was deprecated.
- we are moving towards CRL finally.
there were also some updates in the addons section of the website, and I will update the faq as soon as I can.
if you want to contribute we are working on a librewolf-specific setting page, more details have been shared in the matrix room.
peace 🐠
Welcome to the official community for LibreWolf.
LibreWolf is designed to increase protection against tracking and fingerprinting techniques, while also including a few security improvements. LibreWolf also aims to remove all the telemetry, data collection and annoyances, as well as disabling anti-freedom features like DRM. If you have any question please visit our FAQ first: https://librewolf.net/docs/faq/
To learn more or to download the browser visit the website: https://librewolf.net/
If you want to contribute head over to our Gitlab: https://gitlab.com/librewolf-community/browser
- 0 users online
- 1 user / day
- 3 users / week
- 3 users / month
- 59 users / 6 months
- 354 subscribers
- 40 Posts
- 210 Comments
- Modlog
Looking forward to the Linux release. Good job, everyone.
May I ask, what is CRL? Is it an abbreviation for Certificate Revocation List? Or is it something else?
yes, mozilla implementation is particularly good imo, if you’re curious about it here’s a good read.
Thank you. The article looks really interesting. I will have a look.
If I keep geo location disabled, then I’m more fingerprintable… OK, I think I’ll keep having geo location disabled though, I want to keep that piece of privacy…
The dark mode override being depricated is sad. Theming is always complex for FF and derivatives alone, and if keeping RFP enabled (which is a must now a days) then it might be theeming gets wrong under RFP, but I’ll have to see the effect once upgrading. I’m waiting for artix (universe) to upgrade…
Thanks a lot !
keep in mind that in order for your location to be accessible you have to allow the website to access it manually, otherwise it will be denied. if you don’t even want to be prompted (eg. you think it is annoying) you can disable that in the settings, disabling the api completely is just defense in depth but it is a bit of an extreme threat model for us and it has the fingerprinting tradeoff attached to it.
I knew this was going to be a bit of a controversial one, but there are very good reasons to deprecate it (it’s all in the reference issues and it is quite technical so I won’t repeat it here). for users that care about fingerprinting this makes RFP better for everyone, while those who do not care about it and do not want to live with the downsides of RFP can just disable it. everyone has its own tolerance and that’s totally fine imo. RFP is all or nothing, annoying for some but very powerful :-)
btw your general browser theming will be fine, this applies only to how websites look.
yeah, I’m afraid web sites will all be white/clear now, or break the site theming somehow :(
I can disable RFP, but then I need to figure out what useragent to use, since that’s provided by RFP… Is there an easy way to find the right useragent to use? I remember if I just use Libewolf latest, extensions get broken, and perhaps what I need is FF latest version, though no sure what would be the exact useragent. But I might have to disable FRP then, I’ll have to see how things look, when the new release becomes available, :(
And I prefer totally disabling geo location as well, though that whether or not disabling RFP…
What perhaps would be somehow more important short term is finding out the right useragent each release. So I can set it up, without setting RFP…
Thanks !
extensions still work with the non-RFP user agent, you just need to click an extra button on mozilla’s extension store when you install them. if you are going to change your user agent do not lie about the browser engine or the OS, these are easily detected. I generally do not recommend changing it, but if you really need to, the equivalent firefox version is your best bet I guess.
with that being said, now that you mention it, it would be nice if we could find a way to avoid changing the user agent as part of the librewolf branding. it is not intentional and it is something that we could consider patching (eg. TOR always shows as Firefox, even without RFP).
yey, thanks !
As a follow up @fishonthenet@lemmy.ml, RFP respects dark themes when configured on the web site side. I guess that’s controlled through cookies, and as long as the configuration cookies are kept, one can keep it’s already configured dark theme. I didn’t undertand that from your comment, neither from librewolf-rfp.
I did test letterboxing, and it’s really ugly to my taste, so hopefully you don’t make it default, :). BTW, I’m back to RFP then, yey
yup, manually set themes will stick as long as the cookies are not cleared. also a fellow RFP user is always a great news.
as a follow up I’m very happy to report that I’ve successfully built with the new wasm sandboxing, re-release coming in a few hours :-) win should also be fixed and linux is still having some trouble.
the solution was to use an external sdk + an external dependency with an extra library imported manually. basically a whole mess.