2.0.5 on Solaris with openssl 0.9.8h
Alan, and all , I am facing some challenges on building Freeradius 2.0.5 (Solaris OS) with openssl version 0.9.8h. The Solaris 10 come with prebuilt openssl version, and found at /usr/sfw/bin/openssl, version 0.9.7d. Prior to building freeradius I built newer version openssl (v.0.9.8h) located in /usr/local/ssl. here are the two openssl version now I have in my Solaris. bash-3.00# openssl version OpenSSL 0.9.8h 28 May 2008 bash-3.00# /usr/sfw/bin/openssl version OpenSSL 0.9.7d 17 Mar 2004 (+ security patches to 2006-09-29) When I built Freeradius 2.0.5 (I simply executed three comands, ./configure make and make install) , I was expecting that it would build with my desired openssl version. Aparantly, I found that certain has algorithm (sha256) is not supporting when I work with freeradius (I mean with SSL version that it was built with). However openssl version 0.9.8h should support this. I sent openssl community this question, they wanted me to verify whether I actualy built the freeradius with this new openssl version. I am not able to understand what library it is actually built with, because I could not figure out from build log, nor the configure. But if I use the configure options as below, I see a rolling error (that telling me that I must not have built the freeradius with openssl 0.9.8h ?) : ....... (see portion of my out when I executed make, after ./configure ./configure \ --prefix=/usr/local/freeradius \ --with-openssl=yes \ --with-openssl-dir=/usr/local/ssl \ --with-openssl-includes=/usr/local/ssl/include \ --with-openssl-libraries=/usr/local/ssl/lib ) RB5 -c peap.c -o peap.o >/dev/null 2>&1 /export/home/dev/freeradius-server-2.0.5/libtool --mode=link gcc -release 2.0.5 \ -module -export-dynamic -o rlm_eap_peap.la \ -rpath /usr/local/lib rlm_eap_peap.lo peap.lo rlm_eap_peap.c peap.c /export/home/dev/f radius-server-2.0.5/src/lib/libfreeradius-radius.la ../../libeap/libfreeradius-eap.la usr/local/ssl/lib -lcrypto -lssl -lcrypto -ldl -lnsl -lresolv -lsocket -lposix4 -lpth d gcc -shared -Wl,-h -Wl,rlm_eap_peap-2.0.5.so -o .libs/rlm_eap_peap-2.0.5.so .libs/rlm p_peap.o .libs/peap.o -R/export/home/dev/freeradius-server-2.0.5/src/lib/.libs -R/exp /home/dev/freeradius-server-2.0.5/src/modules/rlm_eap/libeap/.libs -R/usr/local/lib -L port/home/dev/freeradius-server-2.0.5/src/lib/.libs /export/home/dev/freeradius-server 0.5/src/lib/.libs/libfreeradius-radius.so ../../libeap/.libs/libfreeradius-eap.so -L/u local/ssl/lib -lssl -lcrypto -ldl -lnsl -lresolv -lsocket -lposix4 -lpthread -lc Text relocation remains referenced against symbol offset in file <unknown> 0x0 /usr/local/ssl/lib/libssl.a(ssl_lib.o) <unknown> 0x4 /usr/local/ssl/lib/libssl.a(ssl_lib.o) <unknown> 0x8 /usr/local/ssl/lib/libssl.a(ssl_lib.o) <unknown> 0xc /usr/local/ssl/lib/libssl.a(ssl_lib.o) <unknown> 0x10 /usr/local/ssl/lib/libssl.a(ssl_lib.o) <unknown> 0x14 /usr/local/ssl/lib/libssl.a(ssl_lib.o) <unknown> 0x18 /usr/local/ssl/lib/libssl.a(ssl_lib.o) <unknown> 0x1c /usr/local/ssl/lib/libssl.a(ssl_lib.o) <unknown> 0x20 /usr/local/ssl/lib/libssl.a(ssl_lib.o) <unknown> 0x24 /usr/local/ssl/lib/libssl.a(ssl_lib.o) <unknown> 0x28 /usr/local/ssl/lib/libssl.a(ssl_lib.o) <unknown> 0x2c /usr/local/ssl/lib/libssl.a(ssl_lib.o) <unknown> 0x30 /usr/local/ssl/lib/libssl.a(ssl_lib.o) <unknown> 0x34 /usr/local/ssl/lib/libssl.a(ssl_lib.o) <unknown> 0x38 /usr/local/ssl/lib/libssl.a(ssl_lib.o) <unknown> 0x3c /usr/local/ssl/lib/libssl.a(ssl_lib.o) <unknown> 0x40 /usr/local/ssl/lib/libssl.a(ssl_lib.o) On 8/7/08, Rafiqul Ahsan <rafiqul.ahsan@gmail.com> wrote:
I changed the Makefile for random file creation step (as a fix for my earlier posted error)...
This is what I found at Makefile :
random: @if [ -e /dev/urandom ] ; then \ dd if=/dev/urandom of=./random count=10 >/dev/null 2>&1; \ else \ date > ./random; \ fi
I Changed to ...
random date > ./random;
That solved my earlier problem, and now my server is listening.
Thanks, Rafi
On 8/7/08, Rafiqul Ahsan <rafiqul.ahsan@gmail.com> wrote:
I see below error when I execute bootstrap
bash-3.00# /usr/local/etc/raddb/certs/bootstrap ............................................... make: Nothing to be done for `ca'. make: Nothing to be done for `server'. make: `dh' is up to date. /bin/sh: test: argument expected make: *** [random] Error 1
On 8/7/08, Alan DeKok <aland@deployingradius.com> wrote:
Rafiqul Ahsan wrote:
Thanks, I was able to build freeradius 2.0.5 on Solaris 10. However, server is not running, and I see below error when I run "radiusd -X". Here is the output. ... make_cert_command = "/usr/local/etc/raddb/certs/bootstrap" } Exec-Program output:
It's trying to run the bootstrap command. It's not working.
Run the bootstrap command by hand, and then re-start the server.
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
-- Rafiqul Ahsan
-- Rafiqul Ahsan
-- Rafiqul Ahsan
Rafiqul Ahsan wrote:
I am facing some challenges on building Freeradius 2.0.5 (Solaris OS) with openssl version 0.9.8h. The Solaris 10 come with prebuilt openssl version, and found at /usr/sfw/bin/openssl, version 0.9.7d. Prior to building freeradius I built newer version openssl (v.0.9.8h) located in /usr/local/ssl. here are the two openssl version now I have in my Solaris.
Why not just install the OpenSSL from sunfreeware? They have a package pre-built...
When I built Freeradius 2.0.5 (I simply executed three comands, ./configure make and make install) , I was expecting that it would build with my desired openssl version.
Why? How does it know what you desire? Did you configure the linker to prefer one version over the other? Did you configure the C "include" references to prefer one over the other?
this. I sent openssl community this question, they wanted me to verify whether I actualy built the freeradius with this new openssl version.
Well... of course.
I am not able to understand what library it is actually built with, because I could not figure out from build log, nor the configure. But if I use the configure options as below, I see a rolling error (that telling me that I must not have built the freeradius with openssl 0.9.8h ?) :
No idea. ...
Text relocation remains referenced against symbol offset in file <unknown> 0x0 /usr/local/ssl/lib/libssl.a(ssl_lib.o)
That's a fairly useless error. Are you sure that the libssl.a file is really a library, and not something else? Alan DEKok.
Alan DeKok escribió:
Rafiqul Ahsan wrote:
I am facing some challenges on building Freeradius 2.0.5 (Solaris OS) with openssl version 0.9.8h. The Solaris 10 come with prebuilt openssl version, and found at /usr/sfw/bin/openssl, version 0.9.7d. Prior to building freeradius I built newer version openssl (v.0.9.8h) located in /usr/local/ssl. here are the two openssl version now I have in my Solaris.
Why not just install the OpenSSL from sunfreeware? They have a package pre-built...
When I built Freeradius 2.0.5 (I simply executed three comands, ./configure make and make install) , I was expecting that it would build with my desired openssl version.
Why? How does it know what you desire? Did you configure the linker to prefer one version over the other? Did you configure the C "include" references to prefer one over the other?
this. I sent openssl community this question, they wanted me to verify whether I actualy built the freeradius with this new openssl version.
Well... of course.
I am not able to understand what library it is actually built with, because I could not figure out from build log, nor the configure. But if I use the configure options as below, I see a rolling error (that telling me that I must not have built the freeradius with openssl 0.9.8h ?) :
No idea. ...
Text relocation remains referenced against symbol offset in file <unknown> 0x0 /usr/local/ssl/lib/libssl.a(ssl_lib.o)
That's a fairly useless error. Are you sure that the libssl.a file is really a library, and not something else?
Alan DEKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
I'm not sure and i'm not an expert, but *.a files are only headers files. Cross-compiling wpa_supplicant i had to use it (libssl32.a i remember) and, because is a only headers file, i had to use it's equivalent *.dll file, which it IS a library. Also i don't know anything about "h" version of openssl but i have debian with openssl package that comes in the installation and a compiled version by me too. In theory you only need to tell compiler where are the libraries, header files etc.
Sergio wrote:
I'm not sure and i'm not an expert, but *.a files are only headers files.
Uh... no. It's a *static* library.
Cross-compiling wpa_supplicant i had to use it (libssl32.a i remember) and, because is a only headers file, i had to use it's equivalent *.dll file, which it IS a library.
On Windows. Solaris isn't Windows, and doesn't use .dll. Alan DeKok.
I tried to install the openssl from Sunware, but it installs at /usr/local/ssl directory. Somehow (could not figure out how) the freeradius build process linking with the Solaris prebuilt openssl library at /usr/sfw.. I would like to change configuration the linker to prefer one version (0.9.8)over the other (0.9.7 is prebuilt comes with Solaris).. also to include references to prefer one over other...But I don;t know where to change.I looked at Configure, Makefile....but cannot seem to find where it was configured that. Can you please help ? Thanks On 8/13/08, Alan DeKok <aland@deployingradius.com> wrote:
Rafiqul Ahsan wrote:
I am facing some challenges on building Freeradius 2.0.5 (Solaris OS) with openssl version 0.9.8h. The Solaris 10 come with prebuilt openssl version, and found at /usr/sfw/bin/openssl, version 0.9.7d. Prior to building freeradius I built newer version openssl (v.0.9.8h) located in /usr/local/ssl. here are the two openssl version now I have in my Solaris.
Why not just install the OpenSSL from sunfreeware? They have a package pre-built...
When I built Freeradius 2.0.5 (I simply executed three comands, ./configure make and make install) , I was expecting that it would build with my desired openssl version.
Why? How does it know what you desire? Did you configure the linker to prefer one version over the other? Did you configure the C "include" references to prefer one over the other?
this. I sent openssl community this question, they wanted me to verify whether I actualy built the freeradius with this new openssl version.
Well... of course.
I am not able to understand what library it is actually built with, because I could not figure out from build log, nor the configure. But if I use the configure options as below, I see a rolling error (that telling me that I must not have built the freeradius with openssl 0.9.8h ?) :
No idea. ...
Text relocation remains referenced against symbol offset in file <unknown> 0x0 /usr/local/ssl/lib/libssl.a(ssl_lib.o)
That's a fairly useless error. Are you sure that the libssl.a file is really a library, and not something else?
Alan DEKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
-- Rafiqul Ahsan
Rafiqul Ahsan wrote:
I tried to install the openssl from Sunware, but it installs at /usr/local/ssl directory. Somehow (could not figure out how) the freeradius build process linking with the Solaris prebuilt openssl library at /usr/sfw..
Because that's what the linker on Solaris does. Go read it's documentation to see how to configure it to do what you want. This isn't a FreeRADIUS question.
I would like to change configuration the linker to prefer one version (0.9.8)over the other (0.9.7 is prebuilt comes with Solaris).. also to include references to prefer one over other...But I don;t know where to change.I looked at Configure, Makefile....but cannot seem to find where it was configured that. Can you please help ?
Maybe the Solaris linker documentation will help? Heck, if you're building as root, just do "chmod a-rwx /usr/sfw", build FreeRADIUS, and then do "chmod a+rx /usr/sqf". That should solve it. i.e. This is pretty much a Unix 101 question... Alan DeKok.
Hi Alan, and All, Well, I believe I have linked Freeradius 2.0.5 with the right openssl (0.9.8h) now by adding below env variables(my build logs also says that linked with -L/usr/local/ssl/lib). However I still see the same error while using sha256 encryption algorithm with RSA 2048 key. I sent this query to openssl maillist, they are sending me back to you (freeradius folks) to verify whether Freeradius supports sha2, sha256 etc. (I hoped that below patch would allow, but no luck). CFLAGS=-I/usr/local/ssl/include/openssl CPPFLAGS=-I/usr/local/ssl/include/openssl LDFLAGS=-L/usr/local/ssl/lib export CFLAGS CPPFLAGS LDFLAGS And earlier I added below two patches to Freeradius: --- freeradius-1.1.7/configure +++ freeradius-1.1.7-new/configure @@ -20552,7 +20552,7 @@ echo $ECHO_N "(cached) $ECHO_C" >&6 else ac_check_lib_save_LIBS=$LIBS -LIBS="-lssl $LIBS" +LIBS="-lssl -lcrypto -ldl $LIBS" cat >conftest.$ac_ext <<_ACEOF /* confdefs.h. */ _ACEOF @@ -20617,8 +20617,7 @@ if test "x$OPENSSL_LIB_DIR" != "x"; then OPENSSL_LIBS="-L$OPENSSL_LIB_DIR" fi - OPENSSL_LIBS="$OPENSSL_LIBS -lcrypto -lssl -lcrypto" - + OPENSSL_LIBS="$OPENSSL_LIBS -lcrypto -lssl -lcrypto -ldl" fi diff -Naur freeradius-1.1.7-mod/src/modules/rlm_eap/types/rlm_eap_tls/rlm_eap_tls.c freeradius-1.1.7/src/modules/rlm_eap/types/rlm_eap_tls/rlm_eap_tls.c --- freeradius-1.1.7-mod/src/modules/rlm_eap/types/rlm_eap_tls/rlm_eap_tls.c 2007-04-20 14:58:46.000000000 +0300 +++ freeradius-1.1.7/src/modules/rlm_eap/types/rlm_eap_tls/rlm_eap_tls.c @@ -292,6 +292,7 @@ */ SSL_library_init(); SSL_load_error_strings(); + OpenSSL_add_all_digests(); meth = TLSv1_method(); ctx = SSL_CTX_new(meth); On 8/14/08, Alan DeKok <aland@deployingradius.com> wrote:
Rafiqul Ahsan wrote:
I tried to install the openssl from Sunware, but it installs at /usr/local/ssl directory. Somehow (could not figure out how) the freeradius build process linking with the Solaris prebuilt openssl library at /usr/sfw..
Because that's what the linker on Solaris does. Go read it's documentation to see how to configure it to do what you want. This isn't a FreeRADIUS question.
I would like to change configuration the linker to prefer one version (0.9.8)over the other (0.9.7 is prebuilt comes with Solaris).. also to include references to prefer one over other...But I don;t know where to change.I looked at Configure, Makefile....but cannot seem to find where it was configured that. Can you please help ?
Maybe the Solaris linker documentation will help?
Heck, if you're building as root, just do "chmod a-rwx /usr/sfw", build FreeRADIUS, and then do "chmod a+rx /usr/sqf". That should solve it. i.e. This is pretty much a Unix 101 question...
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
-- Rafiqul Ahsan
Rafiqul Ahsan wrote:
Hi Alan, and All,
Well, I believe I have linked Freeradius 2.0.5 with the right openssl (0.9.8h) now by adding below env variables(my build logs also says that linked with -L/usr/local/ssl/lib). However I still see the same error while using sha256 encryption algorithm with RSA 2048 key. I sent this query to openssl maillist, they are sending me back to you (freeradius folks) to verify whether Freeradius supports sha2, sha256 etc. (I hoped that below patch would allow, but no luck).
CFLAGS=-I/usr/local/ssl/include/openssl CPPFLAGS=-I/usr/local/ssl/include/openssl LDFLAGS=-L/usr/local/ssl/lib export CFLAGS CPPFLAGS LDFLAGS
I forget. Were you using the Sun toolchain or GNU? You probably need one of: LDFLAGS='-L/usr/local/ssl/lib -Wl,-rpath -Wl,/usr/local/ssl/lib or LDFLAGS='-L/usr/local/ssl/lib -R/usr/local/ssl/lib' or whatever similar incantation your linker wants to achive the same result, forcing it to use the version of openssl in /usr/local/lib -- REALITY.SYS not found: Universe halted.
It is Solaris 10 (V210). Now I have added below Flags (as per your previous email) : CFLAGS=-I/usr/local/ssl/include/openssl CPPFLAGS=-I/usr/local/ssl/include/openssl LDFLAGS='-L/usr/local/ssl/lib -R/usr/local/ssl/lib' export CFLAGS CPPFLAGS LDFLAGS How else to verify that my Frerradius 2.0.5 was built with openssl0.9.8h (Again, please note openssl 0.9.8h was installed in /usr/local/ssl, and prebuilt openssl (came with Solaris 10) 0.9.7 is at /usr/sfw) ? I wanted to build with 0.9.8h because it supports advance crypto like sha2, sha256 etc....But still does not seem like Freeradius is working with sha256. Here is the part of make log : gcc -DHAVE_CONFIG_H -I. -I. -I. -I/usr/local/ssl/include/openssl -I/usr/local/s sl/include/openssl -c ltdl.c -fPIC -DPIC -o .libs/ltdl.o gcc -DHAVE_CONFIG_H -I. -I. -I. -I/usr/local/ssl/include/openssl -I/usr/local/s sl/include/openssl -c ltdl.c -o ltdl.o >/dev/null 2>&1 /bin/bash ./libtool --tag=CC --mode=link gcc -I/usr/local/ssl/include/openssl -no-undefined -version-info 4:4:1 -L/usr/local/ssl/lib -R/usr/local/ssl/lib -o libltdl.la -rpath /usr/local/lib ltdl.lo -ldl gcc -shared -Wl,-h -Wl,libltdl.so.3 -o .libs/libltdl.so.3.1.4 .libs/ltdl.o -R/ usr/local/ssl/lib -L/usr/local/ssl/lib -ldl -lc (cd .libs && rm -f libltdl.so.3 && ln -s libltdl.so.3.1.4 libltdl.so.3) (cd .libs && rm -f libltdl.so && ln -s libltdl.so.3.1.4 libltdl.so) ar cru .libs/libltdl.a ltdl.o ranlib .libs/libltdl.a creating libltdl.la On 8/15/08, Andrew Hood <freeradius@andyhood.net> wrote:
Rafiqul Ahsan wrote:
Hi Alan, and All,
Well, I believe I have linked Freeradius 2.0.5 with the right openssl (0.9.8h) now by adding below env variables(my build logs also says that linked with -L/usr/local/ssl/lib). However I still see the same error while using sha256 encryption algorithm with RSA 2048 key. I sent this query to openssl maillist, they are sending me back to you (freeradius folks) to verify whether Freeradius supports sha2, sha256 etc. (I hoped that below patch would allow, but no luck).
CFLAGS=-I/usr/local/ssl/include/openssl CPPFLAGS=-I/usr/local/ssl/include/openssl LDFLAGS=-L/usr/local/ssl/lib export CFLAGS CPPFLAGS LDFLAGS
I forget. Were you using the Sun toolchain or GNU?
You probably need one of:
LDFLAGS='-L/usr/local/ssl/lib -Wl,-rpath -Wl,/usr/local/ssl/lib
or
LDFLAGS='-L/usr/local/ssl/lib -R/usr/local/ssl/lib'
or whatever similar incantation your linker wants to achive the same result, forcing it to use the version of openssl in /usr/local/lib
-- REALITY.SYS not found: Universe halted. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
-- Rafiqul Ahsan
Rafiqul Ahsan wrote:
It is Solaris 10 (V210). Now I have added below Flags (as per your previous email) :
CFLAGS=-I/usr/local/ssl/include/openssl CPPFLAGS=-I/usr/local/ssl/include/openssl LDFLAGS='-L/usr/local/ssl/lib -R/usr/local/ssl/lib' export CFLAGS CPPFLAGS LDFLAGS
How else to verify that my Frerradius 2.0.5 was built with openssl0.9.8h (Again, please note openssl 0.9.8h was installed in /usr/local/ssl, and prebuilt openssl (came with Solaris 10) 0.9.7 is at /usr/sfw) ? I wanted to build with 0.9.8h because it supports advance crypto like sha2, sha256 etc....But still does not seem like Freeradius is working with sha256.
Here is the part of make log : gcc -DHAVE_CONFIG_H -I. -I. -I. -I/usr/local/ssl/include/openssl -I/usr/local/s sl/include/openssl -c ltdl.c -fPIC -DPIC -o .libs/ltdl.o gcc -DHAVE_CONFIG_H -I. -I. -I. -I/usr/local/ssl/include/openssl -I/usr/local/s sl/include/openssl -c ltdl.c -o ltdl.o >/dev/null 2>&1 /bin/bash ./libtool --tag=CC --mode=link gcc -I/usr/local/ssl/include/openssl -no-undefined -version-info 4:4:1 -L/usr/local/ssl/lib -R/usr/local/ssl/lib -o libltdl.la -rpath /usr/local/lib ltdl.lo -ldl gcc -shared -Wl,-h -Wl,libltdl.so.3 -o .libs/libltdl.so.3.1.4 .libs/ltdl.o -R/ usr/local/ssl/lib -L/usr/local/ssl/lib -ldl -lc (cd .libs && rm -f libltdl.so.3 && ln -s libltdl.so.3.1.4 libltdl.so.3) (cd .libs && rm -f libltdl.so && ln -s libltdl.so.3.1.4 libltdl.so) ar cru .libs/libltdl.a ltdl.o ranlib .libs/libltdl.a creating libltdl.la
Assuming you have run "make install", what does ldd /your/path/to/libltdl.so return? -- REALITY.SYS not found: Universe halted.
Here is the output. Not sure if this ensures the Freeradius built with /usr/local/ssl/lib (0.9.8h), or /usr/sfw (0.9.7). My objective is to build with 0.9.8h (but below output shows libgcc_s.sp.1 located at /usr/sfw/lib). Can you please confirm from below output : # ldd /usr/local/lib/libltdl.so.3.1.4 libdl.so.1 => /lib/libdl.so.1 libc.so.1 => /lib/libc.so.1 libgcc_s.so.1 => /usr/sfw/lib/libgcc_s.so.1 libm.so.2 => /lib/libm.so.2 /platform/SUNW,Sun-Fire-V210/lib/libc_psr.so.1 On 8/16/08, Andrew Hood <freeradius@andyhood.net> wrote:
Rafiqul Ahsan wrote:
It is Solaris 10 (V210). Now I have added below Flags (as per your previous email) :
CFLAGS=-I/usr/local/ssl/include/openssl CPPFLAGS=-I/usr/local/ssl/include/openssl LDFLAGS='-L/usr/local/ssl/lib -R/usr/local/ssl/lib' export CFLAGS CPPFLAGS LDFLAGS
How else to verify that my Frerradius 2.0.5 was built with openssl0.9.8h (Again, please note openssl 0.9.8h was installed in /usr/local/ssl, and prebuilt openssl (came with Solaris 10) 0.9.7 is at /usr/sfw) ? I wanted to build with 0.9.8h because it supports advance crypto like sha2, sha256 etc....But still does not seem like Freeradius is working with sha256.
Here is the part of make log : gcc -DHAVE_CONFIG_H -I. -I. -I. -I/usr/local/ssl/include/openssl -I/usr/local/s sl/include/openssl -c ltdl.c -fPIC -DPIC -o .libs/ltdl.o gcc -DHAVE_CONFIG_H -I. -I. -I. -I/usr/local/ssl/include/openssl -I/usr/local/s sl/include/openssl -c ltdl.c -o ltdl.o >/dev/null 2>&1 /bin/bash ./libtool --tag=CC --mode=link gcc -I/usr/local/ssl/include/openssl -no-undefined -version-info 4:4:1 -L/usr/local/ssl/lib -R/usr/local/ssl/lib -o libltdl.la -rpath /usr/local/lib ltdl.lo -ldl gcc -shared -Wl,-h -Wl,libltdl.so.3 -o .libs/libltdl.so.3.1.4 .libs/ltdl.o -R/ usr/local/ssl/lib -L/usr/local/ssl/lib -ldl -lc (cd .libs && rm -f libltdl.so.3 && ln -s libltdl.so.3.1.4 libltdl.so.3) (cd .libs && rm -f libltdl.so && ln -s libltdl.so.3.1.4 libltdl.so) ar cru .libs/libltdl.a ltdl.o ranlib .libs/libltdl.a creating libltdl.la
Assuming you have run "make install", what does
ldd /your/path/to/libltdl.so
return? -- REALITY.SYS not found: Universe halted. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
-- Rafiqul Ahsan
Looks like I Freeradius still built with openssl 0.9.7 at /usr/swf...here is the ldd output : # ldd /usr/local/sbin/radiusd libfreeradius-radius-2.0.5.so => /usr/local/lib/libfreeradius-ra dius-2.0.5.so libnsl.so.1 => /lib/libnsl.so.1 libresolv.so.2 => /lib/libresolv.so.2 libsocket.so.1 => /lib/libsocket.so.1 librt.so.1 => /lib/librt.so.1 libpthread.so.1 => /lib/libpthread.so.1 libcrypt_d.so.1 => /usr/lib/libcrypt_d.so.1 libltdl.so.3 => /usr/local/lib/libltdl.so.3 libssl.so.0.9.7 => /usr/sfw/lib/libssl.so.0.9.7 libcrypto.so.0.9.7 => /usr/sfw/lib/libcrypto.so.0.9.7 libdl.so.1 => /lib/libdl.so.1 libc.so.1 => /lib/libc.so.1 libgcc_s.so.1 => /usr/sfw/lib/libgcc_s.so.1 libmp.so.2 => /lib/libmp.so.2 libmd.so.1 => /lib/libmd.so.1 libscf.so.1 => /lib/libscf.so.1 libaio.so.1 => /lib/libaio.so.1 libgen.so.1 => /lib/libgen.so.1 libdoor.so.1 => /lib/libdoor.so.1 libuutil.so.1 => /lib/libuutil.so.1 libssl_extra.so.0.9.7 => /usr/sfw/lib/libssl_extra.so.0.9.7 libcrypto_extra.so.0.9.7 => /usr/sfw/lib/libcrypto_extra.so.0.9.7 libm.so.2 => /lib/libm.so.2 /platform/SUNW,Sun-Fire-V210/lib/libc_psr.so.1 /platform/SUNW,Sun-Fire-V210/lib/libmd_psr.so.1 On 8/16/08, Rafiqul Ahsan <rafiqul.ahsan@gmail.com> wrote:
Here is the output. Not sure if this ensures the Freeradius built with /usr/local/ssl/lib (0.9.8h), or /usr/sfw (0.9.7). My objective is to build with 0.9.8h (but below output shows libgcc_s.sp.1 located at /usr/sfw/lib). Can you please confirm from below output :
# ldd /usr/local/lib/libltdl.so.3.1.4 libdl.so.1 => /lib/libdl.so.1 libc.so.1 => /lib/libc.so.1 libgcc_s.so.1 => /usr/sfw/lib/libgcc_s.so.1 libm.so.2 => /lib/libm.so.2 /platform/SUNW,Sun-Fire-V210/lib/libc_psr.so.1
On 8/16/08, Andrew Hood <freeradius@andyhood.net> wrote:
Rafiqul Ahsan wrote:
It is Solaris 10 (V210). Now I have added below Flags (as per your previous email) :
CFLAGS=-I/usr/local/ssl/include/openssl CPPFLAGS=-I/usr/local/ssl/include/openssl LDFLAGS='-L/usr/local/ssl/lib -R/usr/local/ssl/lib' export CFLAGS CPPFLAGS LDFLAGS
How else to verify that my Frerradius 2.0.5 was built with openssl0.9.8h (Again, please note openssl 0.9.8h was installed in /usr/local/ssl, and prebuilt openssl (came with Solaris 10) 0.9.7 is at /usr/sfw) ? I wanted to build with 0.9.8h because it supports advance crypto like sha2, sha256 etc....But still does not seem like Freeradius is working with sha256.
Here is the part of make log : gcc -DHAVE_CONFIG_H -I. -I. -I. -I/usr/local/ssl/include/openssl -I/usr/local/s sl/include/openssl -c ltdl.c -fPIC -DPIC -o .libs/ltdl.o gcc -DHAVE_CONFIG_H -I. -I. -I. -I/usr/local/ssl/include/openssl -I/usr/local/s sl/include/openssl -c ltdl.c -o ltdl.o >/dev/null 2>&1 /bin/bash ./libtool --tag=CC --mode=link gcc -I/usr/local/ssl/include/openssl -no-undefined -version-info 4:4:1 -L/usr/local/ssl/lib -R/usr/local/ssl/lib -o libltdl.la -rpath /usr/local/lib ltdl.lo -ldl gcc -shared -Wl,-h -Wl,libltdl.so.3 -o .libs/libltdl.so.3.1.4 .libs/ltdl.o -R/ usr/local/ssl/lib -L/usr/local/ssl/lib -ldl -lc (cd .libs && rm -f libltdl.so.3 && ln -s libltdl.so.3.1.4 libltdl.so.3) (cd .libs && rm -f libltdl.so && ln -s libltdl.so.3.1.4 libltdl.so) ar cru .libs/libltdl.a ltdl.o ranlib .libs/libltdl.a creating libltdl.la
Assuming you have run "make install", what does
ldd /your/path/to/libltdl.so
return? -- REALITY.SYS not found: Universe halted. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
-- Rafiqul Ahsan
-- Rafiqul Ahsan
Rafiqul Ahsan wrote:
Looks like I Freeradius still built with openssl 0.9.7 at /usr/swf...here is the ldd output :
Follow instructions. If you "chmod a-rx /usr/swf", the linker CANNOT and WILL NOT pick up OpenSSL from that directory. If that causes too many problems, then "chmod a-r /usr/sfw/lib/libssl*" and /usr/sfw/lib/libcrypto*". Really. It's that simple. *Then* build the server. *Then* change the permissions back. Alan DeKok.
Ok, I tried as follows : 1. chmod a-rx /usr/sfw 2. As before I kept below FLAGS on : CFLAGS=-I/usr/local/ssl/include/openssl CPPFLAGS=-I/usr/local/ssl/include/openssl LDFLAGS='-L/usr/local/ssl/lib -R/usr/local/ssl/lib' export CFLAGS CPPFLAGS LDFLAGS 3. ./configure 4. make 5. make install Still "ldd /usr/local/sbin/radiusd" shows the shared object from /usr/sfw/lib/*0.9.7 Here are the outputs when we deleted the permission (before build), and added the permissions (after build) : bash-3.00# chmod a-rx /usr/sfw/ bash-3.00# ls -al /usr/sfw/ total 54 d--------- 11 root bin 512 Aug 1 11:06 . drwxr-xr-x 42 root sys 1024 Aug 5 23:54 .. drwxr-xr-x 3 root bin 6144 Aug 1 11:08 bin lrwxrwxrwx 1 root root 9 Aug 1 11:06 doc -> share/doc drwxr-xr-x 22 root bin 2048 Aug 1 11:08 include lrwxrwxrwx 1 root root 10 Aug 1 11:06 info -> share/info drwxr-xr-x 31 root bin 6656 Aug 13 12:35 lib drwxr-xr-x 3 root bin 512 Aug 1 10:51 libexec lrwxrwxrwx 1 root root 9 Aug 1 10:54 man -> share/man drwxr-xr-x 3 root bin 512 Aug 1 10:50 mysql drwxr-xr-x 2 root bin 512 Aug 1 11:14 sbin drwxr-xr-x 21 root bin 512 Aug 1 11:06 share drwxr-xr-x 4 root bin 512 Aug 1 10:34 sparc-sun-solaris2.10 lrwxrwxrwx 1 root root 9 Aug 1 09:54 src -> share/src drwxr-xr-x 6 root bin 512 Aug 1 09:54 swat bash-3.00# chmod a+rx /usr/sfw/ bash-3.00# ls -al /usr/sfw/ total 54 dr-xr-xr-x 11 root bin 512 Aug 1 11:06 . drwxr-xr-x 42 root sys 1024 Aug 5 23:54 .. drwxr-xr-x 3 root bin 6144 Aug 1 11:08 bin lrwxrwxrwx 1 root root 9 Aug 1 11:06 doc -> share/doc drwxr-xr-x 22 root bin 2048 Aug 1 11:08 include lrwxrwxrwx 1 root root 10 Aug 1 11:06 info -> share/info drwxr-xr-x 31 root bin 6656 Aug 13 12:35 lib drwxr-xr-x 3 root bin 512 Aug 1 10:51 libexec lrwxrwxrwx 1 root root 9 Aug 1 10:54 man -> share/man drwxr-xr-x 3 root bin 512 Aug 1 10:50 mysql drwxr-xr-x 2 root bin 512 Aug 1 11:14 sbin drwxr-xr-x 21 root bin 512 Aug 1 11:06 share drwxr-xr-x 4 root bin 512 Aug 1 10:34 sparc-sun-solaris2.10 lrwxrwxrwx 1 root root 9 Aug 1 09:54 src -> share/src drwxr-xr-x 6 root bin 512 Aug 1 09:54 swat On 8/17/08, Alan DeKok <aland@deployingradius.com> wrote:
Rafiqul Ahsan wrote:
Looks like I Freeradius still built with openssl 0.9.7 at /usr/swf...here is the ldd output :
Follow instructions. If you "chmod a-rx /usr/swf", the linker CANNOT and WILL NOT pick up OpenSSL from that directory.
If that causes too many problems, then "chmod a-r /usr/sfw/lib/libssl*" and /usr/sfw/lib/libcrypto*". Really. It's that simple.
*Then* build the server. *Then* change the permissions back.
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
-- Rafiqul Ahsan
Rafiqul Ahsan wrote:
Ok, I tried as follows : ... Still "ldd /usr/local/sbin/radiusd" shows the shared object from /usr/sfw/lib/*0.9.7
Then the issue is that the linker is linking against "libssl.so", and not "libssl.so.0.9.8". This means that at run-time, /usr/sfw/lib is found *before* /usr/local/lib, and so it links to the other version of libssl. The only solutions are: a) change the order of directories that the run-time linker uses b) delete the /usr/sfw/lib/libssl* files Alan DeKok.
Alan DeKok wrote:
Rafiqul Ahsan wrote:
Ok, I tried as follows :
...
Still "ldd /usr/local/sbin/radiusd" shows the shared object from /usr/sfw/lib/*0.9.7
Then the issue is that the linker is linking against "libssl.so", and not "libssl.so.0.9.8". This means that at run-time, /usr/sfw/lib is found *before* /usr/local/lib, and so it links to the other version of libssl.
The only solutions are:
a) change the order of directories that the run-time linker uses b) delete the /usr/sfw/lib/libssl* files
I haven't tried the method I suggested earlier in this thread on Solaris. I have done it on Linux. For reasons too complex to go into I can not replace the default version of openssl, but I need a later verison to build freeradius. I put that version in the same target directories: openssl config: ./Configure no-shared enable-zlib-dynamic \ --prefix=/opt/freeradius --openssldir=/opt/freeradius/ssl \ linux-elf freeradius configure script: export PKG_CONFIG_PATH=/opt/freeradius/lib/pkgconfig export CC='gcc -march=i686' export F77='g77 -march=i686' export CXX='g++ -march=i686' export LDFLAGS='-Wl,-rpath -Wl,/opt/freeradius/lib' ./configure \ --prefix=/opt/freeradius \ --localstatedir=/var \ --with-openssl-includes=/opt/freeradius/include \ --with-openssl-libraries=/opt/freeradius/lib And it works: $ ldd /opt/freeradius/sbin/radiusd libfreeradius-radius-2.0.5.so => /opt/freeradius/lib/libfreeradius-radius-2.0.5.so (0x40016000) libnsl.so.1 => /lib/libnsl.so.1 (0x4004d000) libresolv.so.2 => /lib/libresolv.so.2 (0x40062000) libpthread.so.0 => /lib/libpthread.so.0 (0x40072000) libsnmp.so.15 => /usr/local/lib/libsnmp.so.15 (0x40087000) libcrypt.so.1 => /lib/libcrypt.so.1 (0x4012e000) libltdl.so.3 => /usr/lib/libltdl.so.3 (0x4015b000) libdl.so.2 => /lib/libdl.so.2 (0x40162000) libssl.so.0.9.8 => /opt/freeradius/lib/libssl.so.0.9.8 (0x40166000) libcrypto.so.0.9.8 => /opt/freeradius/lib/libcrypto.so.0.9.8 (0x401a0000) libc.so.6 => /lib/libc.so.6 (0x402c6000) libcrypto.so.0 => /usr/lib/libcrypto.so.0 (0x403e9000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000) -- REALITY.SYS not found: Universe halted.
I believe I specified the path using -Rpath, and Solaris Linker searches this specified path for so libraris at run time. But still it is linking with /usr/swf/lib.. Did not find any other info on how we change the orders of dirs that it uses. On 8/17/08, Alan DeKok <aland@deployingradius.com> wrote:
Rafiqul Ahsan wrote:
Ok, I tried as follows : ... Still "ldd /usr/local/sbin/radiusd" shows the shared object from /usr/sfw/lib/*0.9.7
Then the issue is that the linker is linking against "libssl.so", and not "libssl.so.0.9.8". This means that at run-time, /usr/sfw/lib is found *before* /usr/local/lib, and so it links to the other version of libssl.
The only solutions are:
a) change the order of directories that the run-time linker uses b) delete the /usr/sfw/lib/libssl* files
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
-- Rafiqul Ahsan
UNCLASSIFIED
-----Original Message----- From: freeradius-users-bounces+frank.ranner=defence.gov.au@lists.fre eradius.org [mailto:freeradius-users-> bounces+frank.ranner=defence.gov.au@lists.freeradius.org] On Behalf Of Rafiqul Ahsan Sent: Monday, 18 August 2008 07:21 To: FreeRadius users mailing list Subject: Re: 2.0.5 on Solaris with openssl 0.9.8h
I believe I specified the path using -Rpath, and Solaris Linker searches this specified path for so libraris at run time. But still it is linking with /usr/swf/lib.. Did not find any other info on how we change the orders of dirs that it uses.
Use ldd -s to determine how the shared libraries are found. The bottom line is, use LD_LIBRARY_PATH to overide all other settings. In your startup script put: LD_LIBRARY_PATH=/usr/lib:/usr/local/ssl/lib; export LD_LIBRARY_PATH You can also specify system-wide library search paths using crle [root@server radius] # crle Configuration file [version 4]: /var/ld/ld.config Default Library Path (ELF): /usr/lib:/usr/local/lib:/var/cfengine/lib Trusted Directories (ELF): /usr/lib/secure (system default) Command line: crle -c /var/ld/ld.config -l /usr/lib:/usr/local/lib:/var/cfengine/lib Using rpath is not such a good idea as it is the last resort - crle and LD_LIBRARY_PATH will override it as 'ldd -s' will show. Regards, Frank Ranner
Thanks for your response. Here is what I set : bash-3.00# crle Configuration file [version 4]: /var/ld/ld.config Default Library Path (ELF): /lib/:/usr/lib:/usr/local/ssl/lib Trusted Directories (ELF): /lib/secure:/usr/lib/secure (system default) Command line: crle -c /var/ld/ld.config -l /lib/:/usr/lib:/usr/local/ssl/lib bash-3.00# echo $LD_LIBRARY_PATH /usr/lib:/usr/local/ssl/lib Looks like the issue is not the search path because it already serached to my desired location /usr/local/ssl/lib before /usr/sfw/lib. The issue is why Freeradius radiusd is looking for object libssl.so.0.9.7 libcrypto.so.0.9.7, and obviously it will not find at /usr/local/ssl/lib ? Here is the (partial) output of ldd -s radiusd find object=libssl.so.0.9.7; required by /usr/local/sbin/radiusd search path=/usr/local/lib:/usr/local/ssl/lib:/usr/sfw/lib (RPATH from file /usr/local/sbin/radiusd) trying path=/usr/local/lib/libssl.so.0.9.7 trying path=/usr/local/ssl/lib/libssl.so.0.9.7 trying path=/usr/sfw/lib/libssl.so.0.9.7 libssl.so.0.9.7 => /usr/sfw/lib/libssl.so.0.9.7 find object=libcrypto.so.0.9.7; required by /usr/local/sbin/radiusd search path=/usr/local/lib:/usr/local/ssl/lib:/usr/sfw/lib (RPATH from file /usr/local/sbin/radiusd) trying path=/usr/local/lib/libcrypto.so.0.9.7 trying path=/usr/local/ssl/lib/libcrypto.so.0.9.7 trying path=/usr/sfw/lib/libcrypto.so.0.9.7 libcrypto.so.0.9.7 => /usr/sfw/lib/libcrypto.so.0.9.7 On 8/17/08, Ranner, Frank MR <Frank.Ranner@defence.gov.au> wrote:
UNCLASSIFIED
-----Original Message----- From: freeradius-users-bounces+frank.ranner=defence.gov.au@lists.fre eradius.org [mailto:freeradius-users-> bounces+frank.ranner=defence.gov.au@lists.freeradius.org] On Behalf Of Rafiqul Ahsan Sent: Monday, 18 August 2008 07:21 To: FreeRadius users mailing list Subject: Re: 2.0.5 on Solaris with openssl 0.9.8h
I believe I specified the path using -Rpath, and Solaris Linker searches this specified path for so libraris at run time. But still it is linking with /usr/swf/lib.. Did not find any other info on how we change the orders of dirs that it uses.
Use ldd -s to determine how the shared libraries are found. The bottom line is, use LD_LIBRARY_PATH to overide all other settings. In your startup script put:
LD_LIBRARY_PATH=/usr/lib:/usr/local/ssl/lib; export LD_LIBRARY_PATH
You can also specify system-wide library search paths using crle
[root@server radius] # crle
Configuration file [version 4]: /var/ld/ld.config Default Library Path (ELF): /usr/lib:/usr/local/lib:/var/cfengine/lib Trusted Directories (ELF): /usr/lib/secure (system default)
Command line: crle -c /var/ld/ld.config -l /usr/lib:/usr/local/lib:/var/cfengine/lib
Using rpath is not such a good idea as it is the last resort - crle and LD_LIBRARY_PATH will override it as 'ldd -s' will show.
Regards, Frank Ranner
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
-- Rafiqul Ahsan
Rafiqul Ahsan wrote:
... The issue is why Freeradius radiusd is looking for object libssl.so.0.9.7 libcrypto.so.0.9.7,
Because of the linker. This has nothing to do with RADIUS. It has nothing to do with FreeRADIUS. If all else fails, build the server on *another* machine which *doesn't* have /usr/sfw/, and then copy the binaries && libraries over to the first machine. Alan DeKok.
Hi Alan, Thank you for your responses, and I appreciate for your time. I have few Sun machines, T2000, V210 - all of them has Solaris 10 with /usr/sfw/ dirs...Not sure I would try deleting the directory. But before going in to that approach, I have done a little test.... 1. I moved libssl.so.0.9.7, and libcrypto.so.0.9.7 from /usr/sfw/lib directory, and copied libssl.0.9.8, and libcrypto.0.9.8 in to this directory. 2. Having following path, and FLAGS... bash-3.00# echo $PATH /usr/sbin:/usr/bin:/usr/local/ssl/bin:/usr/sfw/bin:/usr/local/bin:/usr/ccs/bin bash-3.00# echo LDFLAGS LDFLAGS bash-3.00# echo $LDFLAGS -L/usr/local/ssl/lib -R/usr/local/ssl/lib bash-3.00# echo $CPPFLAGS -I/usr/local/ssl/include/openssl bash-3.00# echo $CFLAGS -I/usr/local/ssl/include/openssl bash-3.00# crle Configuration file [version 4]: /var/ld/ld.config Default Library Path (ELF): /lib/:/usr/lib:/usr/local/ssl/lib Trusted Directories (ELF): /lib/secure:/usr/lib/secure (system default) Command line: crle -c /var/ld/ld.config -l /lib/:/usr/lib:/usr/local/ssl/lib bash-3.00# echo $LD_LIBRARY_PATH /usr/lib:/usr/local/ssl/lib 3. ./configure --prefix=/usr/local --with-openssl-includes=/usr/local/s sl/include --with-openssl-libraries=/usr/local/ssl/lib See the below WARNING : configure: WARNING: pcap library not found, silently disabling the RADIUS sniffer. config.status: WARNING: ./Make.inc.in seems to ignore the --datarootdir setting config.status: WARNING: ./src/include/build-radpaths-h.in seems to ignore the --datarootdir setting chmod: WARNING: can't access check-radiusd-config configure: WARNING: silently not building rlm_counter. configure: WARNING: FAILURE: rlm_counter requires: libgdbm. configure: WARNING: silently not building rlm_eap_tls. configure: WARNING: FAILURE: rlm_eap_tls requires: OpenSSL. configure: WARNING: silently not building rlm_eap_ttls. configure: WARNING: FAILURE: rlm_eap_ttls requires: OpenSSL. configure: WARNING: silently not building rlm_eap_ikev2. configure: WARNING: FAILURE: rlm_eap_ikev2 requires: libeap-ikev2 EAPIKEv2/connector.h. configure: WARNING: the TNCS library isn't found! configure: WARNING: silently not building rlm_eap_tnc. configure: WARNING: FAILURE: rlm_eap_tnc requires: -lTNCS. configure: WARNING: silently not building rlm_eap_peap. configure: WARNING: FAILURE: rlm_eap_peap requires: OpenSSL. configure: WARNING: silently not building rlm_ippool. configure: WARNING: FAILURE: rlm_ippool requires: libgdbm. configure: WARNING: neither krb5 'k5crypto' nor 'crypto' libraries are found! configure: WARNING: the comm_err library isn't found! configure: WARNING: silently not building rlm_krb5. configure: WARNING: FAILURE: rlm_krb5 requires: krb5.h. configure: WARNING: silently not building rlm_ldap. configure: WARNING: FAILURE: rlm_ldap requires: libldap_r. configure: WARNING: silently not building rlm_otp. configure: WARNING: FAILURE: rlm_otp requires: openssl-libs. configure: WARNING: silently not building rlm_perl. configure: WARNING: FAILURE: rlm_perl requires: EXTERN.h perl.h libperl.so. configure: WARNING: silently not building rlm_python. configure: WARNING: FAILURE: rlm_python requires: Python.h libpython2.3. configure: WARNING: silently not building rlm_sql_iodbc. configure: WARNING: FAILURE: rlm_sql_iodbc requires: libiodbc isql.h. configure: WARNING: silently not building rlm_sql_postgresql. configure: WARNING: FAILURE: rlm_sql_postgresql requires: libpq. configure: WARNING: oracle headers not found. Use --with-oracle-home-dir=<path>. configure: WARNING: silently not building rlm_sql_oracle. configure: WARNING: FAILURE: rlm_sql_oracle requires: oci.h. configure: WARNING: silently not building rlm_sql_unixodbc. configure: WARNING: FAILURE: rlm_sql_unixodbc requires: libodbc sql.h. 4. Make --- never creates rlm_eap_ttls/tls.o 5. Make install creates new radiusd...but with no libssl.so.0.9.X, and libcrypto.so.0.9.X Here is the output... # ldd /usr/local/sbin/radiusd libfreeradius-radius-2.0.5.so => /usr/local/lib/libfreeradius-ra dius-2.0.5.so libnsl.so.1 => /lib//libnsl.so.1 libresolv.so.2 => /lib//libresolv.so.2 libsocket.so.1 => /lib//libsocket.so.1 librt.so.1 => /lib//librt.so.1 libpthread.so.1 => /lib//libpthread.so.1 libcrypt_d.so.1 => /usr/lib/libcrypt_d.so.1 libltdl.so.3 => /usr/local/lib/libltdl.so.3 libdl.so.1 => /lib//libdl.so.1 libc.so.1 => /lib//libc.so.1 libgcc_s.so.1 => /usr/sfw/lib/libgcc_s.so.1 libmp.so.2 => /lib//libmp.so.2 libmd.so.1 => /lib//libmd.so.1 libscf.so.1 => /lib//libscf.so.1 libaio.so.1 => /lib//libaio.so.1 libgen.so.1 => /lib//libgen.so.1 libdoor.so.1 => /lib//libdoor.so.1 libuutil.so.1 => /lib//libuutil.so.1 libm.so.2 => /lib//libm.so.2 /platform/SUNW,Sun-Fire-V210/lib/libc_psr.so.1 /platform/SUNW,Sun-Fire-V210/lib/libmd_psr.so.1 I am confused !!!!! ....I see it likes , and ONLY likes libssl.so.0.9.7, and libcrypto.so.0.9.7 at /usr.sfw/lib ... Rafi On 8/18/08, Alan DeKok <aland@deployingradius.com> wrote:
Rafiqul Ahsan wrote:
... The issue is why Freeradius radiusd is looking for object libssl.so.0.9.7 libcrypto.so.0.9.7,
Because of the linker. This has nothing to do with RADIUS. It has nothing to do with FreeRADIUS.
If all else fails, build the server on *another* machine which *doesn't* have /usr/sfw/, and then copy the binaries && libraries over to the first machine.
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
-- Rafiqul Ahsan
Rafiqul Ahsan wrote:
Thank you for your responses, and I appreciate for your time. I have few Sun machines, T2000, V210 - all of them has Solaris 10 with /usr/sfw/ dirs...
I would suggest asking Sun for help with this issue. It's a problem specific to Solaris, and in the end, has very little to do with FreeRADIUS.
3. ./configure --prefix=/usr/local --with-openssl-includes=/usr/local/s sl/include --with-openssl-libraries=/usr/local/ssl/lib
See the below WARNING :
<sigh> You've just managed to ignore most of the output of configure, and everything related to how it finds OpenSSL. I have no idea why you think this is useful. Alan DeKok.
participants (5)
-
Alan DeKok -
Andrew Hood -
Rafiqul Ahsan -
Ranner, Frank MR -
Sergio