zlacker

[parent] [thread] 2 comments
1. novok+(OP)[view] [source] 2022-07-30 02:48:38
I think if owners of devices have ultimate control over the root key / credential that determines attestation, I don't think people care about that.

So in your case, for devices you buy, you set up your corporate TPM key as the root owner, and then you send the device to employees, vendors, etc. The ownership chain is clear and you can send attestation requests. The corp is the owner of the device, and that is fairly obvious.

The issue is when people and corps buy devices, they do not have effective root. Microsoft, apple, google, etc have the tpm root key, and you as a corporation actually do not have root yourself. They can force you to do things you want to do. It makes you more vulnerable, because if it is in MSFTs interest (or they are coerced by the state to do so clandestinely) a lot of threats can happen, and you don't even need an 0day to do so!

If it starts becoming status quo, the freedom to do the things you need to your devices starts going away.

replies(1): >>jauer+31
2. jauer+31[view] [source] 2022-07-30 03:06:41
>>novok+(OP)
> The issue is when people and corps buy devices, they do not have effective root.

Totally!

The answer isn't to ban the tech, it's to ensure that everyone can set their own root if they so choose.

Want your system to only load firmware that's been signed by Debian to ensure that unfree blobs aren't sneaking in? Great! That's basically what we want too (s/Debian/our own supply chain integrity folks/g but same concept).

replies(1): >>novok+i2
◧◩
3. novok+i2[view] [source] [discussion] 2022-07-30 03:26:23
>>jauer+31
The thing is, it's effectively impossible to politically guarantee that, so rather ban attestation than walk a fine line of 'your not allowed to do that'.
[go to top]