26 Jan
2007
26 Jan
'07
2:01 a.m.
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.
Yes. Endian issues, etc.
Is there any reason freeradius-client couldn't use the same MD5.c/h at FreeRADIUS?
That's the goal: To have more of a shared code base. For now, it could be done with a little bit of hacking. Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog