Upstream Changes https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop_01744469280.html What's Changed docs: note presence of other packages in repo by @HastD in #980 cho...

Upstream Changes https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop_018223192.html What's Changed fix(aarch64): skip emulated vm for sanity check on aarch64 by @RoyalO...

Would be cool to see other hardened browsers compared such as Vanadium, Iron Fox, and Trivalent (on SecureBlue vs not on SecureBlue).

As a huge Secureblue fan, I’d also be interested in seeing Trivalent listed

As a huge Secureblue fan, I’d also be interested in seeing Trivalent listed

v4.10 - Fedora 45 Reminder: releases are symbolic. Builds are created and published immediately after new commits are merged. Secureblue has switched to Fedora 45 base images. As usual, users do no...

Upstream Changes https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop.html What's Changed feat(cicd): add automated sanity check with screenshot by @RoyalOughtness in #9...

November 2026 | AI, Cybersecurity, Linux and the Future of Digital Protection Artificial intelligence is changing the cybersecurity landscape at a remarkable pace. It is helping security researcher…

Duplicate of Installing tor browser on secureblue - #58 by RoyalOughtness

A few months ago there was a response about this from the developer of secureblue: Installing tor browser on secureblue Questions > There’s a lot of stuff to respond to in here, so I’m gonna do it all in one big post. In the future though please direct these questions to our Discord . Distro Box a warning about this practice. Yes, the warning is just to inform the user not to treat Distrobox as a sandboxing tool So what is the recommended way to install Tor on Secureblue? I would recommend using it in a VM. We recently shipped virt-manager OOTB, which you can use to provision a VM for Tor Browser. FAQ | secur…

What's Changed chore(deps): bump step-security/harden-runner from 2.22.1 to 2.22.2 by @dependabot[bot] in #946 chore(deps): bump github/codeql-action/upload-sarif from 4.39.0 to 4.39.1 by @dependa...

What's Changed chore(deps): bump zizmorcore/zizmor-action from 0.6.4 to 0.7.1 by @dependabot[bot] in #942 chore(deps): bump github/codeql-action/upload-sarif from 4.38.3 to 4.39.0 by @dependabot[b...

LunarBeacon45: > I am on secureblue after a lot of bounching around. It certainly does mitigate a significant number of vulnerabilities from stock fedora but it comes at the cost of a bit of a learning curve and constantly needing to tweak things. I don’t know that I can recommend it unless you have a more elevated threat model as I do or a high tolerance for bs. Could you give some examples of problems you have with SecureBlue, what didnt work?

Really as unfortunately as it is to say, the most secure OS in the modern day for the average user is MacOS. QubesOS is also excellent but not practical for average users and FreeBSD/OpenBSD are likely more secure than linux in general but good luck using those on a desktop. I am on secureblue after a lot of bounching around. It certainly does mitigate a significant number of vulnerabilities from stock fedora but it comes at the cost of a bit of a learning curve and constantly needing to tweak things. I don’t know that I can recommend it unless you have a more elevated threat model as I do or a high tolerance for bs. I think a significant number of linux issues, though not all, can be remediated by just understanding how to effectively use Linux in a safer manner. I have 3 recommendations that I feel mitigate the majority of issues. 1. Use Flatpaks flatpak solves many of the sandboxing issues that linux has, while not perfect it is probably the best option today. whenever possible I choose to download apps from flatpak over through the distro package manager 2. Encrypt your file system If you don’t encrypt your file system, your data is basically just sitting there. If something were to happen like your computer is stolen, they have full access to everything no matter what else you do. This is a pretty important baseline imo 3. Stop using sudo There was a time where this was unimaginable to me. I was punching in my sudo password 5 times a day, I couldn’t imagine not having sudo on my computer but after switching to secureblue I realized how poor this practice really is and now I think all desktop distros should stop encouraging it. While sudo is really helpful on servers where other hardening is done and system files constantly need to be updates, on desktop linux with proper package management like flatpak, you can live in the userspace most of the time and not need a direct pipeline to root access to your system. Secureblue uses run0 with a seperate admin account for when you do need elevated permissions, I use my fingerprint for authentication and a seperate password to make it easy, and after a few days it really stopped being an issue. None of this is a perfect solution, and even with secureblues additional security hardening like kernel security, hardened memory allocator, and security defaults, it still can’t beat BSDs or MacOS, but I at least feel we can be more secure than Windows while having much better privacy.

What's Changed feat: add JIT control feature to chrome://flags by @RKNF404 in #931 chore: add check for log level being a number by @RKNF404 in #934 chore: various minor GPU sandbox improvements b...

Secureblue is actually pretty viable for a home server. For a commercial one you might need the extra resources and support present in redhat or debian, but secureblue isn’t too bad. OpenBSD is famous, but probably not great if you aren’t a BSD person. At least, it would take a lot of effort to learn. Sometimes software doesn’t behave the same in BSD as well. I had memory errors with Syncthing in netbsd no matter what I did. Okay, what does mine look like? I tried to use Macos as a server, but it was too annoying, and I tried to use Secureblue as a desktop, but it was too annoying. Using them the other way around has gone better. My Secureblue setup has server stuff in podman containers when possible.

A security-focused desktop and server Linux operating system.

Honestly, I would stick with Fedora or try Secureblue rather than switching back to Windows just because of those security comparisons. Windows has its own attack surface and privacy trade offs, so its not automatically the better choice. Secureblue is worth considering if you want stronger security defaults without giving up a normal desktop experience. Since you also play Steam games, check compatibility with your usual games and anti-cheat systems before migrating. For an average user, keeping the system updated, using a browser with strong security protections, and avoiding untrusted software will make a big difference regardless of which OS you choose.

Qubes OS is a must, but SecureBlue is a good option also if you want to keep user friendliness.