End-Of-Life hardware in Qubes-certified computers

[fsflover]

Here are some relevant posts:

@adw

In light of QSB-081, should the inclusion criteria be expanded to require that the device’s CPU continues to receive microcode updates? Unfortunately, it looks like this would eliminate all but two of the recommended 4.1 models…

@fsflover

@Sven

What about certified hardware?

I guess it should have a disclaimer, otherwise people might be deceived, thinking that it’s more secure than it actually is.

(I still think it’s necessary)

@adw

marmarek says, “Generally, having microcode updates for certified hardware makes sense. But I think in this specific case, it isn’t the end of the world just yet. And we need to change our approach to sys-net/sys-usb anyway (even if we have microcode updates).”

Short list of laptops/desktops that work well with Qubes OS

Will add my 2 cents here, while navigating through XSA/QSB is really not so easy for end users/anybody really, to have a clear view on status of things but added blind faith in protection without proper compartmentalization/prevention hygiene improvements that should be part of Qubes learning curve since meltdown/spectre of 2019 which literally tinted the sky to a constant ever reddish tone since then, which should influence since then Qubes learning curve to be conscious of what is in computer …