@dylangerdaly atm, I'm only signing the packages going into https://privacyshark.zero-credibility.net/.
Since everything is built on various runners, it's unfortunately only semi-possible to show things remain untampered; although we could at least calculate and show the checksums of the artifacts after the build, so people can verify they at least got what was build with a specific pipeline/job. those resulting packages could, of course, then be signed again.
@shreyasminocha signing commits would certainly make a lot of sense as well indeed!
--with-system-nss, which is probably why it doesn't work on your system)
It's ok with AppImage but it runs like a portable app, I tried to install the flatpack release but the install command ouput me this:
luca@luca-ubuntu:~/Scaricati$ flatpak install LibreWolf-75.0-1.x86_64.flatpak
Note that the directories
are not in the search path set by the XDG_DATA_DIRS environment variable, so
applications installed by Flatpak may not appear on your desktop until the
session is restarted.
error: The application io.gitlab.LibreWolf/x86_64/master requires the runtime org.gnome.Platform/x86_64/3.36 which was not found
Is gnome required? Im on KDE Plasma
flatpak install– I'll need to investigate this at some point.
flatpak --user remote-add --from flathub https://flathub.org/repo/flathub.flatpakrepoand
flatpak --user install flathub org.gnome.Platform//3.36(or without the
--useroption for both commands if you want to install things system wide).
Good to hear :)
Hm, that should work; there are probably two reasons why this might still happen: it's either an issue with the Flatpak (although if it stores configuration changes you made, that would indicate that access to your local storage / home directory works – it worked for me at least when I tried it), or it might be caused by the somewhat restrictive default settings LibreWolf is shipped with (intentionally). If you feel like it, you can see if some of the other settings with regards to history and session management might be the issue – but I'll try to check it myself as well and get back to you :)
Sounds like it, yeah. Unless that's "all" about those issues, it might be relatively simple to disable even further down the road when building from source (ie. modifying the included css-files which define the styles for it) – but if there's "more to it" (does it include any new, problematic behaviour, eg. sending your typing somewhere), it might get more complicated ^^
I'll look into it ^^