librewolf homebrew installation is damaged

[sbklein]

I think this occurred from the latest update to librewolf. Whenever I try to open it, the computer tells me its damaged and should be trashed.
I tried reinstalling it, and when that didn't work I also forced the cache to remove all installs so that the .dmg file would be downloaded again. Reinstalling with that newly downloaded librewolf is still damaged.
I then downloaded it manually from librewolf's website and installed to Applications, keeping both versions. The manual download works without an issue, the homebrew copy is still corrupted.
Is anyone having similar issues? Should I submit an issue to the homebrew-cask branch?

[flowoy96]

Hey, this is due to macOS's Gatekeeper. Just reinstall LibreWolf with the following flag:

brew reinstall librewolf --no-quarantine

This should solve the problem :)

[Bug-Reaper]

2023 and it's still like this. It's a shame we can't get a properly signed libre-wolf dmg as unsandboxed web browser that is slow to recieve security updates feels very meh. That said, huge shoutouts to the libre-wolf team. This is a labor of love and apple does make proper sign a PITA especially when multiple binaries are bundled. Perhaps one day I'll look to properly sign/notarize this.

[Jolg42]

Same issue here with latest version 117.0-1/librewolf-117.0-1-macos-arm64-package.dmg

I tried brew install --cask librewolf but got this damaged issue.

brew reinstall librewolf --no-quarantine was necessary to make it successful.

[Jolg42]

It looks like the tracking issue was closed

https://gitlab.com/librewolf-community/browser/macos/-/issues/19
Now moved to https://codeberg.org/librewolf/issues/issues/710

[AllThePi]

Just commenting to say this is still the case for me on 1/24/24

[justinnichols]

And still happening on Sonoma 14.4 on an M2 Macbook Air. If, perchance, any Librewolf devs see this...if we're supposed to install with --no-quarantine then perhaps the installation instructions for macOS on the main website should state this.

[lightnin]

Still happening Sonomo 14.5 on M3.
Would it be possible to change the brew instruction set so that we did not have to reinstall with the --no-quarantine flag after each update? Or does it require action by librewolf maintainers?

[mrtysn]

Same issue on M2 Max chip with MacOS Sonoma 14.6.1. The fix below still works.

brew reinstall librewolf --no-quarantine