Package Details: librewolf-bin 1:152.0.6_1-1

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.net/
Keywords: browser web
Licenses: MPL-2.0
Conflicts: librewolf
Provides: librewolf
Submitter: lsf
Maintainer: lsf
Last Packager: lsf
Votes: 644
Popularity: 19.83
First Submitted: 2019-06-16 13:12 (UTC)
Last Updated: 2026-07-15 08:05 (UTC)

Required by (40)

Sources (7)

Pinned Comments

lsf commented on 2021-11-10 12:14 (UTC) (edited on 2026-05-07 09:38 (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 662E3CDD6FE329002D0CA5BB40339DD82B12EF16 should 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 :)

/edit: (2026-05-07): The upstream signing sub-key was rotated, and the .tar.xz tarballs will now be signed with a new subkey. The main key id (0x662E3CDD6FE329002D0CA5BB40339DD82B12EF16) remains unchanged though, so should you get an error during signature verification about a missing (sub)key, all that's required would be to refresh the key(s) via gpg --refresh-keys 662E3CDD6FE329002D0CA5BB40339DD82B12EF16.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 .. 29 Next › Last »

lsf commented on 2025-11-29 23:45 (UTC) (edited on 2025-11-29 23:51 (UTC) by lsf)

I really should stop reading comments. Guess I never learn.

Anyway: PRs for the project are, of course, always very welcome; and the way to address severe lack of current core maintainers (we once were four? five?, now we're like… one and a half, all put together, maybe, depending on how one wants to count?) of a project with a surprisingly large userbase would be… drumroll… for folks to step up and (help to) do the work? If not, well: it will die sooner rather than later. Or probably just stagnate and fizzle out.

/edit: oh, lone-cloud! Now I remember that name. Well known for (now deleted) previous comments not great in tone or helpfulness. Well, thanks, I guess?

ParadiseofMagic commented on 2025-11-29 13:04 (UTC)

@beluga2 Firefox version 145.0.2 was tagged the day you flagged this. Librewolf doesn't perfectly follow Firefox releases, please check https://gitlab.com/librewolf-community/browser/bsys6/-/tags before flagging. If you wish to send an issue to upstream(Librewolf themselves), please go to https://codeberg.org/librewolf/issues/issues but please be patient. It will take some time before they update to the newest release.

Please remember that this package while maintained by upstream is not where you should sending issues about Librewolf. This package only gets the latest release(binary) thus the -bin suffix, I understand you are new to the AUR please check out https://wiki.archlinux.org/title/Arch_User_Repository . This wiki page contains information on AUR packages and how to use the AUR, the FAQ is particularity helpful.

lone-cloud commented on 2025-11-29 03:17 (UTC)

@olive898 in most cases I would agree with you, but this is the 8th most popular project on AUR with a supposedly huge userbase based on votes. I was hoping that someone would explain to me how this is a good browser. It has come under my attention again recently since it's being spammed with out-of-date flags that the maintainer is not clearing. Notably I didn't know about the PG forums, but they were a great read and for that I thank you. TL;DR: librewolf is a dying browser fork now that its lost its core maintainer (xbrit) last year and the remaining 3 maintainers aren't keeping up. There's no longer a good reason to use librewolf over an alternative.

olive898 commented on 2025-11-27 16:02 (UTC)

@lone-cloud Are you seriously hoping someone will chew you information on AUR comments of all places? If you actually bothered to know why Librewolf isn't listed on Privacy Guides you would have done a quick search on their forum.

Stop being so rude out of nowhere, nobody here owe you anything.

mfmAURuser-name commented on 2025-11-20 19:02 (UTC) (edited on 2025-11-20 19:02 (UTC) by mfmAURuser-name)

Do any of you bother to actually look upstream?

145 was tagged just this morning:

https://codeberg.org/librewolf/source/releases/tag/145.0.1-1

There are/were issues with porting patches to the new version:

https://codeberg.org/librewolf/issues/issues/2721

View the ReadMe for how it's packaged:

https://codeberg.org/librewolf/source#readme

Squidward commented on 2025-11-20 18:38 (UTC)

@lone-cloud The manitainer is sometimes a bit slow on the updates but i dont think this is a horrible thing, they dont do this for money.

as for security, i think you are wrong. librewolf doesnt add or remove any critical part of the web engine, as far as i know the changes are pretty simple but useful things like a hardened default config and all the telemtry removed.

also i have never heard of this website you linked and i dont think they are an authority when it comes to safety and privacy.

lone-cloud commented on 2025-11-20 05:31 (UTC)

@ParadiseofMagic That's cool, but the maintainer of this package has been afk for a while now. It's annoying to me to have to see that this package was flagged out of date by some dumbass and the maintainer isn't clearing the flag. This has been happening for about a week now.

Furthermore, I'm starting to suspect that librewolf is actually a trash, insecure fork. At the time of this writing it's now been about 9 days since firefox 145 came out. That release contains a number of security fixes. I haven't looked into the implications of these security issues, but it's a standard and super vital practice to stay up-to-date with browser updates for the sake of security.

Given that librewolf is not even recommended by https://www.privacyguides.org/en/desktop-browsers/, I suspect that we're a like minded group of dummies who are using an inferior and insecure fork. I'm posting this here in the hopes that somebody will prove me wrong.

ParadiseofMagic commented on 2025-11-18 06:17 (UTC)

@lone-cloud It is possible to unflag a package.

lone-cloud commented on 2025-11-17 18:35 (UTC) (edited on 2025-11-17 18:35 (UTC) by lone-cloud)

There is no 145... yet: https://gitlab.com/librewolf-community/browser/bsys6/-/releases @beluga2 is full of shit. He probably thought that librewolf perfectly follows firefox releases. Is there no way for the maintainer to clear the out-of-date flag?

ParadiseofMagic commented on 2025-11-16 14:38 (UTC)

@beluga2 you've marked this out of date with no link and when I look on Librewolf's Codeberg, the version you listed in the flag doesn't seem to exist. Can you please provide a link of where you found 145.0?