secureblue

This repo uses BlueBuild to generate hardened operating system images, using uBlue's Fedora Atomic-based base images as a starting point. This hardening is done with the following goals in mind:

• Increase defenses against the exploitation of both known and unknown vulnerabilities.
• Avoid sacrificing usability for most use cases where possible

The following are not in scope for this project:

• Anything related to "privacy", since Fedora is already sufficiently private and "privacy" often serves as a euphemism for security theater. This is especially true when at odds with improving security.
• Anything related to "degoogling" chromium. For example, we will not be replacing chromium with Brave or ungoogled-chromium.

What

Hardening applied:

• Setting numerous hardened sysctl values (Inspired by but not the same as Kicksecure's) ^details
• Disabling coredumps in limits.conf
• Disabling all ports and services for firewalld
• Adds per-network MAC randomization
• Blacklisting numerous unused kernel modules to reduce attack surface ^details
• Enabling only the flathub-verified remote by default
• Sets numerous hardening kernel parameters (Inspired by Madaidan's Hardening Guide) ^details
• Installs and enables hardened_malloc globally, including for flatpaks. ^{Thanks to rusty-snake's hardened_malloc spec}
• Installing Chromium instead of Firefox in the base image ^{Why chromium? Why not flatpak chromium?}
• Including a hardened chromium config ^{vanadium comparison} that sets numerous hardened defaults ^details and disables JIT javascript ^why?
• Pushing upstream fedora to harden the build for all fedora users, including secureblue users (for example, by enabling CFI)
• Reduce the sudo timeout to 1 minute
• Disable passwordless sudo for rpm-ostree install ^why?
• Brute force protection by locking user accounts for 24 hours after 50 failed login attempts, hardened password encryption and password quality suggestions
• Installing usbguard and bubblejail
• Set opportunistic DNSSEC and DNSOverTLS for systemd-resolved
• Configure chronyd to use Network Time Security (NTS) ^{using chrony config from GrapheneOS}
• Disable KDE GHNS by default ^why?
• (Non-userns variants) Disabling unprivileged user namespaces
• (Non-userns variants) Replacing bubblewrap with bubblewrap-suid so flatpak can be used without unprivileged user namespaces

Why

Fedora is one of the few distributions that ships with selinux and associated tooling built-in and enabled by default. This makes it advantageous as a starting point for building a hardened system. However, out of the box it's lacking hardening in numerous other areas. This project's goal is to improve on that significantly.

For more info on uBlue and BlueBuild, check out the uBlue homepage and the BlueBuild homepage.

Customization

If you want to add your own customizations on top of secureblue, you are advised strongly against forking. Instead, create a repo for your own image by using the BlueBuild template, then change your base-image to a secureblue image. This will allow you to apply your customizations to secureblue in a concise and maintainable way, without the need to constantly sync with upstream.

FAQ

FAQ

Installation

Have a look at PREINSTALL-README before proceeding.

Rebasing (Recommended)

To rebase a Fedora Atomic installation, choose an $IMAGE_NAME from the list below, then follow these steps:

(Important note: the only supported tag is latest)

• First rebase to the unsigned image, to get the proper signing keys and policies installed:

  rpm-ostree rebase ostree-unverified-registry:ghcr.io/secureblue/$IMAGE_NAME:latest
  

• Reboot to complete the rebase:

  systemctl reboot
  

• Then rebase to the signed image, like so:

  rpm-ostree rebase ostree-image-signed:docker://ghcr.io/secureblue/$IMAGE_NAME:latest
  

• Reboot again to complete the installation

  systemctl reboot
  

ISO

While it's recommended to use a Fedora Atomic iso to install and then rebase that installation to secureblue, you can also generate an iso and install that directly using this script. Please note you should still follow the post-install steps when installing from a generated iso:

./generate_secureblue_iso.sh

Available Images

Without User Namespaces ^{What's the difference?}

general purpose

stable

• kinoite-main-hardened
• kinoite-nvidia-hardened
• bluefin-main-hardened
• bluefin-nvidia-hardened
• aurora-main-hardened
• aurora-nvidia-hardened
• silverblue-main-hardened
• silverblue-nvidia-hardened
• sericea-main-hardened
• sericea-nvidia-hardened

experimental

• cinnamon-main-hardened
• cinnamon-nvidia-hardened
• wayblue-wayfire-main-hardened
• wayblue-wayfire-nvidia-hardened
• wayblue-hyprland-main-hardened
• wayblue-hyprland-nvidia-hardened
• wayblue-river-main-hardened
• wayblue-river-nvidia-hardened
• wayblue-sway-main-hardened
• wayblue-sway-nvidia-hardened

surface ^source

• aurora-surface-hardened
• aurora-surface-nvidia-hardened

asus ^source

• aurora-asus-hardened
• aurora-asus-nvidia-hardened
• silverblue-asus-hardened
• silverblue-asus-nvidia-hardened
• kinoite-asus-hardened
• kinoite-asus-nvidia-hardened

server

• server-main-hardened
• server-nvidia-hardened

With User Namespaces ^{What's the difference?}

general purpose

stable

• kinoite-main-userns-hardened
• kinoite-nvidia-userns-hardened
• bluefin-dx-main-userns-hardened
• bluefin-dx-nvidia-userns-hardened
• bluefin-main-userns-hardened
• bluefin-nvidia-userns-hardened
• aurora-main-userns-hardened
• aurora-nvidia-userns-hardened
• aurora-dx-main-userns-hardened
• aurora-dx-nvidia-userns-hardened
• silverblue-main-userns-hardened
• silverblue-nvidia-userns-hardened
• sericea-main-userns-hardened
• sericea-nvidia-userns-hardened

experimental

• cinnamon-main-userns-hardened
• cinnamon-nvidia-userns-hardened
• wayblue-wayfire-main-userns-hardened
• wayblue-wayfire-nvidia-userns-hardened
• wayblue-hyprland-main-userns-hardened
• wayblue-hyprland-nvidia-userns-hardened
• wayblue-river-main-userns-hardened
• wayblue-river-nvidia-userns-hardened
• wayblue-sway-main-userns-hardened
• wayblue-sway-nvidia-userns-hardened

surface ^source

• aurora-surface-userns-hardened
• aurora-surface-nvidia-userns-hardened
• aurora-dx-surface-userns-hardened
• aurora-dx-surface-nvidia-userns-hardened

asus ^source

• aurora-asus-userns-hardened
• aurora-asus-nvidia-userns-hardened
• aurora-dx-asus-userns-hardened
• aurora-dx-asus-nvidia-userns-hardened
• silverblue-asus-userns-hardened
• silverblue-asus-nvidia-userns-hardened
• kinoite-asus-userns-hardened
• kinoite-asus-nvidia-userns-hardened

server

• server-main-userns-hardened
• server-nvidia-userns-hardened

Post-install

After installation, yafti will open. Make sure to follow the steps listed carefully and read the directions closely.

Have a look at POSTINSTALL-README.

Nvidia

If you are using an nvidia image, run this after installation:

rpm-ostree kargs \
    --append-if-missing=rd.driver.blacklist=nouveau \
    --append-if-missing=modprobe.blacklist=nouveau \
    --append-if-missing=nvidia-drm.modeset=1

Nvidia optimus laptop

If you are using an nvidia image on an optimus laptop, run this after installation:

ujust configure-nvidia-optimus

Contributing

Follow the contributing documentation, and make sure to respect the CoC.

Development

For local Development building locally is the recommended approach.

Community

Opening issues is preferred, but Discord is available as well.