During rpm-ostree operations, it's normal. Outside of that, make sure you followed the nvidia steps in the readme if you're using nvidia.
No, use bubblejail
if there's no flatpak available for an app.
- For flatpaks, remove the
LD_PRELOAD
environment variable via Flatseal. To re-enable hardened_malloc for the respective flatpak, replace the removed variable. - For layered packages and packages installed via brew, run the application with
ujust with-standard-malloc APP
. This starts the app without hardened_malloc only once, it does not disable hardened_malloc for the app persistently.
mitigations=auto,nosmt
is set on secureblue. This means that if your CPU is vulnerable to attacks that utilize Simultaneous Multithreading, SMT will be disabled.
- Check if it's already installed using
rpm -qa | grep x
- For GUI packages, you can install the flatpak if available using the Software store or using
flatpak install
. A catalogue of flatpaks is available at https://flathub.org. - For CLI packages, you can install from brew if available using
brew install
. A catalogue of brew packages is available at https://formulae.brew.sh. - If a package isn't available via the other two options, or if a package requires greater system integration,
rpm-ostree install
can be used to layer rpms directly into your subsequent deployments.
First check if the README already has an equivalent or better feature. If it doesn't, open a new github issue.
ujust install-steam
Bluetooth has a long and consistent history of security issues. However, if you still need it, run:
ujust toggle-bluetooth-modules
This is an issue with rpm-ostree image-based systems generally, and not specific to secureblue. Ideally upgrades would come in the form of a zstd-compressed container diff, but it's not there yet. Check out this upstream issue for more information.
The functionality that provides this, called GHNS, is disabled by default due to the risk posed by the installation of potentially damaging or malicious scripts. This has caused real damage.
If you still want to enable this functionality, run:
ujust toggle-ghns
Xwayland is disabled by default on GNOME, KDE Plasma, and Sway. If you need it, run:
ujust toggle-xwayland
This is because support for installing & using them has been intentionally disabled by default in secureblue. Only GNOME system extensions are trusted, if they are installed.
To enable support for installing GNOME user extensions, you can run ujust command:
ujust toggle-gnome-extensions
If your system time is off by an excessive amount due to rare conditions like a CMOS reset, your network will not connect. A one-time manual reset will fix this. This should never be required except under very rare circumstances.
For more technical detail, see #268
The DNSSEC setting we set in /etc/systemd/resolved.conf.d/securedns.conf
causes known issues with network connectivity when secureblue is used in a VM. To fix it, comment out DNSSEC=allow-downgrade
in that file and manually set a dns provider in network settings.
To subscribe to release notifications, on the secureblue github page, click "Watch", and then "Custom", and select Releases like so:
AppImages depend on fuse2, which is unmaintained and depends on a suid root binary. For this reason, fuse2 support is removed by default. It's strongly recommended that you find alternative mechanisms to install your applications (flatpak, distrobox, etc). If you can't find an alternative and still need fuse2, you can add it back by layering something that depends on it.
For example:
rpm-ostree install zfs-fuse
Similar to the AppImage FAQ, the KDE Vault default backend cryfs
depends on fuse2. For this reason it's recommended that you migrate to an alternative that doesn't depend on fuse2, for example fscrypt
. If you don't want to do so, you can add fuse2 back by layering something that depends on it, as described in the AppImage FAQ.
ujust distrobox-assemble
There is an upstream bug. You may need to run:
mkdir -p ~/.config/environment.d && echo "GSK_RENDERER=gl" >> ~/.config/environment.d/gsk.conf
This should no longer be required as of F41: https://discussion.fedoraproject.org/t/gdk-message-error-71-protocol-error-dispatching-to-wayland-display/127927/42
Try starting hardened-chromium
from the commandline by running chromium-browser
. If you get an error about the current profile already running on another device, this is an issue with upstream chromium which can happen when you rpm-ostree update
or rpm-ostree rebase
. To fix this, simply run rm ~/.config/chromium/SingletonLock
.
bubblejail
SHOULD NOT be used on hardened-chromium
, there are issues reported with the pairing and removing the bubblejail
config after it is applied can be difficult. It should also be noted that applying additional sandboxing may interfere with chromium's own internal sandbox, so it can end up reducing security.
On some Nvidia machines, hardened-chromium
defaults to the X11 backend. Since secureblue disables Xwayland by default, this means that you will need to run ujust toggle-xwayland
and reboot, for hardened-chromium
to work.
Why don't some websites that require JIT/WebAssembly work in hardened-chromium even with the V8 Optimizer toggle enabled?
This is an upstream bug that prevents V8 optimization settings from being applied to iframes embedded within a parent website. As a result, WebAssembly may not function on services that use a separate URL for their content delivery network or other included domains, such as VSCode Web (https://github.dev). To make VSCode Web work properly, you need to manually allow V8 optimizations for the CDN by adding https://[*.]vscode-cdn.net
to your list of trusted websites.
Extensions in hardened-chromium
are disabled by default, for security reasons it is not advised to use them. If you want content/ad blocking, that is already built into hardened-chromium
and enabled by default. If you require extensions, you can re-enable them by disabling the Disable Extensions
toggle under chrome://settings/security
, then restart your browser (this toggle is per-profile).
If the extension you installed doesn't work, it is likely because it requires WebAssembly (WASM) for some cryptographic library or some other optimizations (this is the case with the Bitwarden extension). To re-enable JavaScript JIT and WASM for extensions, enable the feature chrome://flags/#internal-page-jit
.