Most likely outdated system packages.
Upgrade required.
(Whonix is based on Kicksecure.)
Technical background:
1 Like
I tested on a fresh install and can confirm that a system upgrade solved this. What I would like to learn now is how does the Tor Browser know that OS is not updated and offers less protection?
- It doesn’t.
- It’s a feature inherited by Firefox.
- All that Tor Browser developers did related to this feature is change project name / website of Firefox to Tor Browser.
- Firefox started to check if unprivileged namespaces are enabled or disabled, and show a warning based on that. (Security features warning links to Firefox installation support page with incomplete info (#43101) · Issues · The Tor Project / Applications / Tor Browser · GitLab)
- Kicksecure (and Whonix, which is based on Kicksecure) disabled unprivileged namespaces in the 17.2.3.7 release. Then released an upgrade to undo disabling unprivileged namespaces due to issue Unprivileged user namespaces / kernel.unprivileged_userns_clone / Can not run flatpak apps / AppImages after Kicksecure update - Support - Kicksecure Forums.
1 Like
So is this a good or bad change?
It cannot be simplified to the level of good versus bad.
Short of becoming an advanced user, security researcher, developer, or similar, this is not something users can deal with.
This is out of scope for support as per Support Request Policy.
1 Like
Rare to see an answer accompanied by such wise words!