| Git Clone URL: | https://aur.archlinux.org/librewolf-bin.git (read-only, click to copy) |
|---|---|
| Package Base: | librewolf-bin |
| Description: | Community-maintained fork of Firefox, focused on privacy, security and freedom. |
| Upstream URL: | https://librewolf-community.gitlab.io/ |
| Keywords: | browser web |
| Licenses: | GPL, MPL, LGPL |
| Conflicts: | librewolf |
| Provides: | librewolf |
| Submitter: | lsf |
| Maintainer: | lsf |
| Last Packager: | lsf |
| Votes: | 449 |
| Popularity: | 37.04 |
| First Submitted: | 2019-06-16 13:12 (UTC) |
| Last Updated: | 2025-03-06 09:04 (UTC) |
It appears that the latest version 114.0.1-2 broke support for FIDO2 / webauthn?
There's an upstream issue in firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=1836722
As a workaround one can set security.webauthn.ctap2 to false in about:config.
A fix seems to be planned for firefox 116
It appears that the latest version 114.0.1-2 broke support for FIDO2 / webauthn?
All my FIDO2 USB tokens used as 2nd factor are failing on multiple pages (gitlab, nextcloud, etc.). The same tokens work fine when used in Brave browser.
Is there any new setting that needs to be adjusted to re-enable FIDO2 / webauthn support?
I am getting
ERROR: Integrity checks (sha256) differ in size from the source array.
when trying to update to version 112.0.2-1.
It seems that there is a 'SKIP' missing in both sha256sums_x86_64 and sha256sums_aarch64?
The file in question for @Spitap's fix below is:
/home/yourusername/.local/share/applications/librewolf.desktop
Thanks @Spitap!
Hi, as @HurricanePootis said, the desktop file seems a bit broken since 112.0. As suggested on librewolf's Reddit, changing StartupWMClass=LibreWolf to StartupWMClass=librewolf-default fixes the problem.
Is cloning the Librewolf source repo necessary for a couple image files?
@ron2138 Firefox's 'omni.ja's are about the same size as they used to be on (the) previous version(s?) of librewolf - definitely strange...
Replying to dogknowsnx comment from 2023-04-18 16:02 (UTC):
I didn't examine {librewolf-bin,firefox} 111.0.1-1 sizes before replying. Should I? As for 112.0-1,
$ ls -gho /usr/lib/{librewolf,firefox}/{,browser/}omni.ja
-rw-r--r-- 1 39M Apr 10 14:10 /usr/lib/firefox/browser/omni.ja
-rw-r--r-- 1 31M Apr 10 14:10 /usr/lib/firefox/omni.ja
-rw-r--r-- 1 91M Apr 18 01:30 /usr/lib/librewolf/browser/omni.ja
-rw-r--r-- 1 70M Apr 18 01:30 /usr/lib/librewolf/omni.ja
@ron2138 Upon comparing librewolf 111 with 112 it appears that the file 'omni.ja' has exploded somehow - don't know if/why it may differ from firefox's 'omni.ja', though... EDIT: Actually there's two of them: '/usr/lib/librewolf/browser/omni.ja' (91M) and '/usr/lib/librewolf/omni.ja' (70M)
Pinned Comments
lsf commented on 2021-11-10 12:14 (UTC) (edited on 2023-04-17 07:18 (UTC) by lsf)
https://wiki.archlinux.org/title/Arch_User_Repository#Acquire_a_PGP_public_key_if_needed
gpg --keyserver hkp://keyserver.ubuntu.com --search-keys 031F7104E932F7BD7416E7F6D2845E1305D6E801/edit: starting with 112.0-1, the binaries are signed with the maintainers shared key, so
gpg --keyserver hkp://keyserver.ubuntu.com --search-keys 662E3CDD6FE329002D0CA5BB40339DD82B12EF16should do the trick instead. I've also signed the key with the previously used key, so you have at least some guarantee that it's not a malicious attack :)