Hello,

I've installed OpenSSL 0.9.7d in /usr/local/ssl/ on my system and have configured 
freeRADIUS 1.0.0pre3 with:
 --with-openssl-include=/usr/local/ssl/include
 --with-openssl-libraries=/usr/local/ssl/libraries

However after building I end up with radiusd having a dependency on /lib/libssl.so.2 
which just happens to point to the original OpenSSL 0.9.6b library that was originally 
installed on my system. This caused radiusd to crash due to the lack of 
SSL_set_msg_callback in this old library.

Not having much experience with libraries I tried simply redirecting /lib/libssl.so.2 
to point to my new  0.9.7 library and freeRADIUS was happy. But...as you might expect, 
other applications on my platform were not (i.e. Apache). Apparently between 0.9.6b 
and 0.9.7d SSL_add_all_algorithms was replaced by SSL_add_all_algorithms_[no]conf. 
Sigh...

So now I am faced with upgrading all apps on my platform that may have had a 
dependency on OpenSSL 0.9.6b or somehow forcing freeRADIUS to link to the 0.9.7 
library. How do I accomplish this? No matter what I do I end up with that dependency 
on libssl.so.2. Is it possible that I am actually seeing a nested dependency? i.e. 
freeRADIUS relies on another library which in turn relies on OpenSSL 0.9.6b? If so, 
how do I track this down? ldd doesn't  seem to tell me...

Any help would be greatly appreciated.

Thanks,

Larry



- 
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Reply via email to