cert bootstrap script change: no more MD5?

[Arran Cudbard-Bell]

On 18 Oct 2011, at 07:37, Stefan Winter wrote:

> Hi,
> 
>>> the bootstrap script uses ca.cnf, server.cnf and client.cnf for the
>>> generated certificates. All of these set the default_md = md5.
>>> 
>>> iOS 5 is the first OS to condemn certificates which are signed by MD5.
>>> So, the default certificates generated by this script will not be
>>> compatible with recent iOS.
>>> 
>>> Does anything speak against up'ing the default_md to sha1? Otherwise I
>>> can see questions on -user coming up saying EAP doesn't work - and this
>>> time with a particularly difficult to diagnose issue.
>> 
>> is it worth just going straight to eg default_md = sha256 ?
>> 
>> 
>> NIST have already rail-roaded SHA1 out of use..... though I note
>> that openssl < 0.9.8 seem to not like any real crypto for Message Digest :-(
> 
> I'm aware of NISTs specs. What I'm not aware of is the corresponding
> client device support. Is SHA-256 really out on all kinds of EAP-capable
> devices? It would be not so nice to a sizable fraction of (oldish) user
> devices failing authentication because they can't validate the chain due
> to unknown algorithm.
> 
> I really have no idea here - anyone aware of studies, or people already
> running with SHA-256 signatures?
> 
> Greetings,
> 
> Stefan
> 

Didn't we try this before and it broke things? I'm pretty sure this isn't the first time the subjects come up...

Arran Cudbard-Bell
a.cudbardb at freeradius.org

Betelwiki, Betelwiki, Betelwiki.... http://wiki.freeradius.org/ !