Re: [saag] SHA-1 to SHA-n transition

["Hallam-Baker, Phillip" <[e-mail]>]

Thanks Jeff.

At this point I think that it is clear that we can solve this problem, albeit with solutions that are somewhat 'yukky'. The most important questions in my mind are:

* Is the deployment deadlock problem real?
* Is the problem significant enough to add a barnacle to SSL or PKIX?

The problem with barnacles is not the individual barnacle, its the fact that they accumulate and eventually slow the ship down. I don't see the 'yuk' factor as being trivial. On the other hand a deployment deadlock on SHA-n makes me nervous.


-----Original Message-----
From: Jeffrey Hutzelman [mailto:[e-mail]]
Sent: Wed 3/4/2009 11:32 AM
To: Hallam-Baker, Phillip; Peter Gutmann; [e-mail]
Cc: [e-mail]
Subject: RE: [saag] SHA-1 to SHA-n transition
 
--On Wednesday, March 04, 2009 05:34:43 AM -0800 "Hallam-Baker, Phillip" 
<[e-mail]> wrote:

> We are now into the identity issue which has precisley nothing to do with
> algorithm transitions.

Thanks for bringing us back around to the original point.  I'm not sure how 
we got into talking about identity and user credentials, but I seem to 
recall this thread started with a discussion of hash algorithm transition, 
and rather quickly moved away from that topic without any real resolution. 
Can we perhaps get back to discussing a technical problem we can solve, 
instead of one that is outside our expertise?

-- Jeff