Discussion on Purism

As I pointed before @TommyTran732 and to anyone thinking compromising measured boot is trivial, I layed down the tooling for anyone wanting to further protection / prove measured boot not enough to understand and break it once and for all under WiP: introspection - replicate TPM PCRs measurements directly from measured content (TCPA/TPM Event log) by tlaurion · Pull Request #1568 · linuxboot/heads · GitHub

Just use it for the bad to faster the development of something good/better.

Until then, it was proven non trivial. You refusing to read it, test it, prove you understand how a TPM extend/seal/unseal/quote ops work, extract/replay/tamper bootblock anchored measured boot is yet to be proven flawed beyond just theoretical attack by anyone/to everyone. Please just do it and like I said: you’ll get the world’s attention. Until then, you are in denial. And this echo chamber is not the place (not my place) to discuss this further.


EDIT: added repro notes directly at WiP: introspection - replicate TPM PCRs measurements directly from measured content (TCPA/TPM Event log) by tlaurion · Pull Request #1568 · linuxboot/heads · GitHub to entice Evil-Made PoC by anyone willing to take that challenge to move theoretical vuln into a practical, reproducible PoC. Up for the challenge with more than words but code? PLEASE DO IT.

2 Likes

And again, for the sake of this thread, I already replied extensively with my own learnings and criticisms at "Maybe I messed up my qubes installation?" related support questions involving "some" Heads subtleties, aka "How to disable autostarting of service qubes at boot without Grub interface" - #8 by Insurgo

(tags: firmware, testing, security, Purism, QubeOS certification process, oem disk installation, salt, kick-start what should be the next steps, where collaboration is needed etc etc etc)

2 Likes

Do you have the corresponding video?

2 Likes
2 Likes

Direct video link:

2 Likes
I moved this topic to the #all-around-qubes category due to these posts:

If @moderators and/or trust level 3/Regular users would rather prefer the topic goes back into the General Discussion category, simply move it again.

access to category

Isn’t “All around Qubes” somehow access-restricted?
[After checking] → yes it is:

2 Likes
Moved back to `General Discussion`.

It doesn’t seem appropriate to move this mega-thread after all this years. As @fsflover outlined: this is hardware specifically marketed towards Qubes OS users and their experiences and impressions with the vendor are on-topic.

2 Likes

Sure, although Purism primarily targets PureOS, not Qubes OS.

How can I know if the glitter nail polish is acryllic or gel?
I’ve had a very bad experience trying to ask questions about glitter nail polish at local stores that sell glitter nail polish. They always answer “don’t know”.

1 Like

At a glance, thickness of the applied polish is a giveaway. Gel is thicker while acrylic is thinner.

2 Likes

Gel is thicker while acrylic is thinner.

As a straight guy, I wouldn’t know :man_shrugging: :nail_care: :laughing:

1 Like

Trammel recommended this brand. Shipped all privacy beast with it. Worked awesome.

3 Likes

Why are the Purism computers (for example Librem 14) still not certified for Qubes?
Do they not meet its requirements?

1 Like

Assume nobody (from Librem) did start an active cert process together with the QubesOS staff, because none of the certifications for QubesOS were an “easy going” thing. Maybe it will happen one day, but I guess it must be first done through an active doing/inquiry/request from Librem team to Qubes…

Assume also, the Dasharo devices/hardware are very close to the Librem hardware, so nobody really bother about it yet. Librem sells their products rather in the US than overseas…

1 Like

You can search the forum, there are random posts talking about what happened with Purism.

I think they used to be certified, but they tried so sell models that wasn’t certified as certified, so certification was removed from all their models.

Edit:
This post mentions the issue
https://forum.qubes-os.org/t/discussion-on-purism/2627/21

5 Likes

In my opinion, this is completely unfair and harming to Qubes, but:

They did.

Here’s a relevant post: Discussion on Purism - #26 by michael

3 Likes

So, company Purism business interests beat the certification interests? It is sad…

Are there any similar claims against PureOS?
For example, instead of Debian, which unfortunately uses blobs in the kernel and firmware, use PureOS.

1 Like

we have a news page that announced the certification of the Purism Librem 13 in 2015, it was the first Qubes-certified device:

it’s strange to say us not partnering with Purism is harming Qubes, since the business relationship was… harming Qubes? consumers buying certified laptops with different hardware than what was advertised & certified – confusion, needing to troubleshoot, broken functionality… what is the benefit of a certification program that users can’t trust?

in 2021 when Purism offered again their interest in partnering, we discussed it internally and decided not to re-engage with them. our energies instead have gone towards building a more diverse ecosystem of certified hardware providers.

maybe this should be merged with the other thread? was merged :white_check_mark:

2 Likes

You’re contradicting yourself:

In other words, your earlier experience with Purism allowed you to understand that a fixed configuration was important for the Qubes certification – which is perfectly reasonable and fair:

Now, are you saying that Purism refuses to accept this new, reasonable requirement for their next certified product? I don’t understand.

So is this about the non-fixed hardware configuration, or unwritten “ethical requirements”, or maybe because they

? (i. e., they intentionally design their hardware to work with Qubes – is this not a good thing?)

Are bad Internet reviews from haters influencing your decision on who should be certified? I read then all and most of them are mistaken concerning the intentions of the company and consequences for the users (saying this as a user).

So you decided to exclude some hardware providers in order to diversify the ecosystem? This doesn’t sound reasonable at all.

1 Like