[arcurn]

Thanks for the question! I addressed some of this in an answer above: https://news.ycombinator.com/item?id=28129362

The summary version is that we share source code and platform control registers (PCRs) with enterprise customers who need these kind of security guarantees, and also expose the Nitro Enclaves attestation documents to them so they can establish secure channels with E3 in a provable way.

[dannyw]

So basically: as a retail consumer, we can't trust you. You might as well as be a malicous honeypot. Scan and log for cryptocurrency keys and then "get hacked" and retire in Thailand.

Or maybe you're a government honeypot, like Crypto AG, or the numerous other cryptography companies that turned out to actually be mass decryption companies.

If you're building an encryption company, the onus is on you to prove it. BitWarden for example is fully open source, and you can self host the server.

[arcurn]

Hey Danny, correct — we do not currently expose attestations to consumers. Over time, this is something we absolutely plan on doing.

One thing worth focusing on is that Evervault is built for developers. Developers do not have to build using Evervault, so a developer using Evervault to mislead their customers about their security isn't something we focus heavily on. There are much easier ways for developers to mislead customers about their security, but that's a conversation for another time :)

I completely agree re: the onus being on us to prove it. It's something we're actively trying to improve, and sharing how we built E3 is just the beginning of us sharing more about how we design & build. Transparency is an existential requirement for us to become a standard part of the developer toolkit. Watch this space!

[0des]

I agree, the justifications in this thread rely a lot on inherent trust of the facilities provided. I get that your example is somewhat a bad-case-scenario, but today nothing is a surprise, and it's entirely possible as unfortunate as that is.