"i'm running inside a TEE" isn't verification. you have to publish audited, reproducible builds, that generate the key material, and somehow attest that the key was generated inside a process launched from a reproducible build on a TEE, in order to close the loop
and nitro doesn't even provide a means of key attestation. so you can run outside the TEE and just tell people you're running inside one ๐คท๐ปโโ๏ธ
TEE's aren't magic. they're a very specific capability, and one that's only valuable to the operator. this is the same problem that lexe and maple ai face
h/t @semisol
Login to reply
Replies (4)
The signed attestation document can include custom data and a public key, in Nitro.
But the problem is what happens if the Cashu TEE restarts, where are the keys?
Don't worry - he's gonna wear the gimp costume when he signs up for google cloud
yes we're doing all that, no idea what you're rambling about
KMS