Re: [Rats] Out-of-band key material set up in architecture document

[Henk Birkholz <[e-mail]>]

Hi Dave,
hi list,

the scope of the architecture was discussed a lot. It is okay to provide 
a bigger picture here, as the "phasing approach" will allow to talk 
about the attestation provisioning flows later on. Ben accompanied that 
decision process and I think he might be able to restate that :)

I think we are all in wild agreement here wrt to:

> "the manufacturer must put it there”, is however I think too narrow

We do not have to be prescriptive about any things here anyways, but to 
be descriptive or illustrative is very helpful.

In this quite prominent scenario:

> In some arguably more secure designs, the device itself creates the key pair and the manufacturer per se never knows the private key, only the public key,

the manufacturer provisioned something that made this happen (and 
therefore took measures to render the public key meaningful).

Viele Grüße,

Henk

On 06.11.19 17:58, Laurence Lundblade wrote:
> 
> 
>> On Nov 5, 2019, at 3:40 PM, Dave Thaler <[e-mail] 
>> <mailto:[e-mail]>> wrote:
>>
>> Inline below…
>> *From:*RATS <[e-mail] <mailto:[e-mail]>>*On 
>> Behalf Of*Laurence Lundblade
>> *Sent:*Tuesday, November 5, 2019 12:17 PM
>> *To:*[e-mail] <mailto:[e-mail]>
>> *Subject:*[Rats] Out-of-band key material set up in architecture document
>> An issue I have with both the current architecture documents is that 
>> they do not discuss the need for some out of band key material set up 
>> to make verification work.
>>
>>     The manufacturer of the device must put some private key into each
>>     device so that the device can sign attestation evidence. Most
>>     likely the manufacturer also creates the verifying key material,
>>     but they may or may not be the verifier.  If they are not the
>>     verifier, somehow the verifier of attestation evidence must have
>>     corresponding key material to verify the signature.
>>
>> This paragraph could be a start of the text. I think this is a 
>> critical part of the architecture because attestation doesn’t work 
>> without it.
>> I agree that a private key is needed in each device for attestation to 
>> work (at least using any techniques
>> I’m aware of). Saying “the manufacturer must put it there”, is however 
>> I think too narrow, as it implies the
>> manufacturer actually knows the key. In some arguably more secure 
>> designs, the device itself creates the
>> key pair and the manufacturer per se never knows the private key, only 
>> the public key, so it would be
>> confusing to say the manufacturer “put” it there, or that the 
>> “manufacturer creates” the key material.
> 
> We could say “establish the signing key”? Certainly don’t want to 
> exclude those more secure designs.
> 
>> ...
>> Furthermore, the RATS charter does not constrain attestation to only 
>> **hardware** based roots of trust.
>> There are some cases where it may be in a hypervisor or bios or 
>> firmware or whatever, and only attest
>> things above that, with obviously a weaker level of security than 
>> hardware-rooted attestation.   But any
>> protocol mechanisms should still work (mainly because it’s almost 
>> impossible to rule them out except via
>> a security policy that says which keys to trust), even if it’s not the 
>> primary focus we care most about.  The
>> point here being that in such a case it may not be the “manufacturer”, 
>> but may be another entity.  That’s
>> actually true in some cases even for hardware-based roots of trust.
> 
> Yes, the “manufacturer” could be a SW vendor or even the author of a 
> dumb Android app. We need a much broader term or description.
> 
> LL
> 
> 
> _______________________________________________
> RATS mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/rats
>