Re: problems with ldap + ssl + eap-ttls

David Hart [EMAIL PROTECTED] wrote: I remain where I was originally. If I use openssl from the RedHat distribution as the default and mangle the Makefiles for eap-tls and eap-ttls to use the newer libraries, eap and ldap authentication work happily together, but I can't secure the ldap

Re: problems with ldap + ssl + eap-ttls

On Wed, 2004-04-14 at 10:16, Alan DeKok wrote: I think this will require a few more patches to the server, as OpenSSL isn't thread-safe (I don't know why...) Has switching to OpenSSL thread-safe callbacks as opposed to protecting OpenSSL calls with a mutex ever been explored? -- --Mike

Re: problems with ldap + ssl + eap-ttls

[EMAIL PROTECTED] 4/9/2004 9:37:16 PM David Hart [EMAIL PROTECTED] wrote: I assume this is due to an openssl problem, so as an experiment I compiled freeradius to use the current openssl libraries for all modules (configure --with-openssl-libraries=... --with-openssl-includes=...). Did you

problems with ldap + ssl + eap-ttls

environment: latest freeradius from CVS RedHat Linux 8 with openssl-0.9.6b-35.8 RPM openssl-0.9.7c installed from source eDirectory 8.7.1 LDAP server Cisco AP1220 access point MeetingHouse Aegis client 2.2.0.28 doing EAP-TTLS/PAP By installing a modern openssl and following the instructions at