On Thu 25 Jan 2007 22:34, Chris Parker wrote:
Following up my own email, after further digging, it appears that this is an MD5 related issue.
FreeRADIUS uses it's own MD5.c, based on public domain implementation from OpenBSD. Client uses an MD5.c that is from RSA.
I seem to recall there being issues with this in the past, which is why FreeRADIUS forces it's own MD5 to be used.
Is there any reason freeradius-client couldn't use the same MD5.c/h at FreeRADIUS?
OK. Well everyone has chimed in with an OK, so please go ahead and commit it and update the ChangeLog This may warrent a new client release as a broken md5 implimentation is not exactly usefull :-) Cheers -- Peter Nixon http://www.peternixon.net/ PGP Key: http://www.peternixon.net/public.asc