https://librewolf-community.gitlab.io/install/
There's a way to install on kali through .deb, appimages and flatpaks, all of them nicely documented on the link above.
All VPNs are blocked. The only ones that work, are the ones that go through SSL (so that it,s not obvious that it's a VPN connection)
Even those (like the new Stealth feature of ProtonVPN) stop working after they find the IP and blacklist it.
I don't know anything about I2P. I'll have a look. Thanks.
Then, like the other guy suggested, Tor might be your best bet (and also learn how to tunnel your entire system traffic through tor!) But it definitely won't be for watching YouTube. If your currency is worth nothing, try mining any crypto currency - 5€ a month is enough for a good VPN (Mullvad) and should be possible, even with a bad PC. Just a suggestion if your government locks down your country even more or Tor is simply not doing the Job anymore. Stay safe!
I haven't looked at it for a while, but a while ago I found these issues: https://github.com/microsoft/winget-cli/issues/179 https://github.com/microsoft/winget-cli/issues/279
There's an opt-out by now (not sure how obvious that is from the documentation, though), but considering MS's track record, I take little stock in it being completely telemetry-free with this option.
I've not examined the password manager yet. I'm using Keepass and lastpass.com
Perhaps this setting in librwolf.cfg is the culprit:
defaultPref("network.http.windows-sso.enabled", false); // disable MS auto authentication via sso
setting this value to 'true' in your librewolf.overrides.cfg might help.
it most likely won't keep your settings. if you want them to be gone, make sure you use a clean profile and also make sure you don't have any override file as it will surely be picked up by librewolf.
also, if you want to clean leftovers this is where you should look
1.) .exe files are Windows executables- they won't work on Mac
2.) The reason why there isn't a ready-made .dmg is probably because the developers haven't set up the right build pipeline/ infrastructure for it (yet). I would assume that they would need to sign the executable with a valid Apple Developer account (that subscription has an annual fee) for it to "just work" out of the box.
3.) The first thing I always do on a Mac is install homebrew. It's really handy, and then you can just do
brew install git
in the Terminal to install git, for example.
Lastly, I needed to run
codesign --force --deep --sign - /Applications/LibreWolf.app
to get LibreWolf working on M1. This last step wasn't in the repo instructions for some reason.
If I understand you correctly, you are on Debian (non-SID) or Ubuntu?
If so: yep, that's still an open issue – we currently only have a repo build on / for Debian SID. It's a much requested "feature" to also provide builds for Ubuntu (and maybe even stable Debian) – we'll hopefully get to this soon.
It's already noted with the installation instructions on https://librewolf-community.gitlab.io/install/, but it would, of course, be preferable if this wasn't even an issue at all ^^
Wrong.. read the docs and see what its purpose is because it seems you're misunderstanding what the browser is for: https://librewolf-community.gitlab.io/docs/
'Fuckups', or disliked features, on the other hand, are completely subjective. You may not personally like 'View image' being replaced with 'Open image in new tab', but another person doesn't mind it.