Subject: [EAT] some sample attesations

From: "Smith, Ned" <[email-masked]>
Date: Fri, 7 Sep 2018 00:38:18 +0000

It may be useful to distinguish between key attestation (the environment that protects keys during storage and/or use) and environment attestation where other trust relevant code could execute. It is often the case that trusted code is needed beyond crypto algorithms. For example, boot code, SW update and distributed consensus code might be relevant for ‘trusted environments’ where attestation evidence might be presented and checked in a timely way.

I’m not suggesting key attestation is less important code, only that it doesn’t end here. Nevertheless, starting here might make sense.
-Ned

|I've been working with key attestations for the past few months targeting
|a few different platforms in support of certificate issuance. I posted a
|collection of attestation artifacts, corresponding X.509 certificates and
|trust anchors for use in verifying the attestations here:
|https://github.com/Purebred/SampleAttestations. In most cases, the
|attestations were encoded as attributes in SCEP requests.