Conversation

Jarkko Sakkinen

the next piece sliced from tpm2sh: https://crates.io/crates/tpm2-vtpm

Still in very early phases. Now my micro ecosystem has:

1. tpm2-protocol
2. tpm2-crypto (software crypto for doing TPM2 related operations like generating encrypted seeds).
3. tpm2-policy-language
4. tpm2-tpmkey
5. tpm2-vtpm

I think what I get right vs. TSS2 etc. that I'm not building a "big SDK" but instead of common sense re-usable components not enforcing architecture or policy.

#linux #rustlang #tpm
3
1
4
and also i did the one thing right at the bottom that sort of enables all these great components: wrote a decent marshaller/unmarshaller. This is mostly ignored and complex stuff built on top :-)
0
0
0

@jarkko Cool! This is coming just in time for TPM APIs to get a say in 's APIs. There, we're mostly abstracting between microcontroller APIs and verified software crypto. Bul to paraphrase Erich Kästner: No interface is worth reading for embedded if it isn't also worth reading for bigger computers.

0
0
0