If you use Fedora Media Writer to write Silverblue to your USB stick, it automatically verifies the checksum/sig
when you install secureblue, it pulls the unverified image first to pull the pubkey and then automatically rebases you into the signed image on firstrun.
Was gonna reply this sad news. As for the reason why, is this because of the use of wlroots or other libraries, or simply the security just hasnāt been built into the compositors? Context is that Iām interested in developing one for fun, but Iād want to see what you think is the major security flaws.
Iām really enjoying the ublue KDE image (Aurora-dx).
IMHO the KDE team has been really quite responsive on the development front over the last few years, and subsequently itās become a very polished DE.
Even the Fedora SIG recently promoted KDE Plasma to Official status, standing alongside Workstation.
Any efforts to expand to match Fedoraās āequal treatmentā would be fantastic.
Secureblue on qubes would be a killer feature. Next up is a secureblue implementation of whonix. Essentially a gateway for tor. Except not made from Debian garbage.
There has been some chatter in the discord about using secureblue as a base image for some kind of āprivacy imageā. It would be an independent project not affiliated with secureblue, so this is just an FYI that there are others interested in working on it.
Hopefully you all can collaborate and form a project around it