Re: [keyassure] Opening issue #21: "Need to specify which crypto

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

OK, how about this

Define code points for

SHA2-256
SHA2-512
SHA3-256 (reserved)
SHA3-512 (reserved)

If SHA3 is ready in time (i.e. we are still not ready in 2012) we could
consider making SHA3-256 the required algorithm. If not make SHA2-256 and
SHA2-512 the required algorithms.


I don't see the objective here being 'algorithm agility' like we were
fixated on in the 90s. We are not picking eight algorithms with a similar
level of security in the hope that one of them is going to be secure.

What we are doing here is coping with the fact that at the moment we do not
have an industry standard digest function that we can be completely happy
with and we are currently in the mid point of a transition.


On Fri, Mar 4, 2011 at 7:46 AM, Martin Rex <[e-mail]> wrote:

> Warren Kumari wrote:
> >
> > After watching the thread, I'd like to propose this as a strawman:
> >
> > Mandatory to implement algorithms are SHA-256 and SHA-384.
> > For now, these are all we specify.
> >
> > 2: Having more than 1 algorithm forces implementations to understand that
> > there is not just one, and so should help lead towards algorithm agility
>
> I'm OK with defining SHA-256 plus another, stronger hash for use with DANE
>
> I'm OK with mandating SHA-256.
>
>
> I do NOT buy the assertion that it is necessary to have _two_mandatory_
> algorithms for algorithm agility.  For other protocols in the security
> area, one single manadatory and additional recommended&optional
> algorithms are perfectly sufficient.
>
> SHA-384 also looks like an oddball to me.  For agility and interop tests,
> defining SHA-512 should be fine.  I would expect that by the time
> we need to move away from SHA-256, there is a SHA-3 available, and
> it would be OK for DANE to move from SHA-256 mandatory to SHA-3 manadatory
> without ever making SHA-512 mandatory (only recommended).
>
> -Martin
> _______________________________________________
> keyassure mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/keyassure
>



-- 
Website: http://hallambaker.com/