Success PEAP/MSCHAPv2 + LDAP + Samba passwords

2004-11-10 Thread Christophe Boyanique
Hi there, just to confirm previous posts about this type of configuration: it works! Freeradius 1.0.1 Fedora Core 1 OpenLDAP with NT and LM hashed samba password OpenSSL I don't know it there is a bug in freeradius, but the radeapclient is not linked correctly by libtool. Instead of the binary, th

Re: Success PEAP/MSCHAPv2 + LDAP + Samba passwords

2004-11-10 Thread Stefan . Neis
Hi, > OpenLDAP with NT and LM hashed samba password After having read similar stuff several times in the past weeks, what's the real advantage of using NT or LM hashed passwords over using simple clear text passwords? At least securitywise, I can't see any. Regards,

RE: Success PEAP/MSCHAPv2 + LDAP + Samba passwords

2004-11-10 Thread Berry, William
Title: RE: Success PEAP/MSCHAPv2 + LDAP + Samba passwords Personally think that clear text is bad as anyone intercepting the packets can easily pick up anything in clear text. If one knows specifically that traffic is one a completely secure path from end to end then not such an issue. This

RE: Success PEAP/MSCHAPv2 + LDAP + Samba passwords

2004-11-10 Thread Stefan . Neis
Hi, > Personally think that clear text is bad as anyone intercepting the > packets can easily pick up anything in clear text. You mean intercepting the packets between LDAP server and RADIUS server (since the communication with the RADIUS client isn't affected anyway)? But knowing the LM

Re: Success PEAP/MSCHAPv2 + LDAP + Samba passwords

2004-11-10 Thread Alan DeKok
"Berry, William" <[EMAIL PROTECTED]> wrote: > Personally think that clear text is bad as anyone intercepting the packets > can easily pick up anything in clear text. RADIUS passwords are encrypted. Connections from FreeRADIUS to an LDAP server should be encrypted using ldaps, or starttls. Us

Re: Success PEAP/MSCHAPv2 + LDAP + Samba passwords

2004-11-10 Thread Alan DeKok
Christophe Boyanique <[EMAIL PROTECTED]> wrote: > I don't know it there is a bug in freeradius, but the radeapclient is > not linked correctly by libtool. Instead of the binary, the libtool > wrapper remains in the installed path. I tried on Debian unstable (with > included or system libtool) an