Re: [Anima-bootstrap] [Spasm] SHA1 usage in Anima-bootstrap voucher yang

[Russ Housley <[e-mail]>]

Michael:

> Russ Housley <[e-mail]> wrote:
>> I’m sure you know that there are three important properties for hash
>> functions.  The are:
> 
> Yes.
> 
>> In the system you describe, it seems that an attacker would need to
>> find a preimage.  For SHA-1, we do not know of a way to do that yet,
>> but the 160-bit have value produced by SHA-1 is probably not big enough
>> to be considered safe in today's computing environment.
> 
>> It seems very odd to be developing a new standards that is using a hash
>> function that was deprecated at the end of 2010 by NIST.
> 
>> My personal recommendation ould be to move from SHA-1 to SHA-256.
> 
> Yes, I agree completely.
> 
> What I'm asking for, is if there is a good, well-established container that
> we can reference, that essentially gives us the agility to move from SHA1 to
> SHA256, and to SHA3 if we have to.
> 
> Alternatively, for the use case involved, which is to refer to a certificate
> by reference-to-CA + reference-to-DN, if there is some other construct that
> would better do what we want, and *also* provide us with the agility we would
> like.
> 
> (Some ownership vouchers may sit in filing cabinets for a few decades in
> a warehouse somewhere)


As Sean said, RFC 7093 gives ways that the CA can compute the Subject Key Identifier, and the CA can migrate from SHA-256 if needed in the future.

Russ