[Tor-BSD] Having issues forcing Tor release to build with update libssl.so.32.0 library

teor teor2345 at gmail.com
Mon Jun 15 04:51:30 EDT 2015

> On 15 Jun 2015, at 12:29 , Seth <list at sysfu.com> wrote:
> Just updated on OpenBSD 5.7 system to LibresSLL 2.2.0 and built latest release of Tor against it with the following configure line:
> # ./configure --disable-asciidoc --disable-gcc-hardening --sysconfdir=/etc --with-openssl-dir=/usr/local/lib
> This has always worked in the past but for some reason the tor executable is linked to the older (2.1) version of LibreSSL libssl library '/usr/lib/libssl.so.32.0'.
> It does however use the newer libcrypto library '/usr/local/lib/libcrypto.so.33.0'
> $ ldd /usr/local/bin/tor
> /usr/local/bin/tor:
>        Start            End              Type Open Ref GrpRef Name
>        00000f35b0000000 00000f35b062e000 exe  1    0   0      /usr/local/bin/tor
>        00000f38807a4000 00000f3880bb9000 rlib 0    1   0      /usr/lib/libz.so.5.0
>        00000f3897600000 00000f3897a28000 rlib 0    1   0      /usr/lib/libm.so.9.0
>        00000f3821b14000 00000f3821f20000 rlib 0    1   0      /usr/lib/libevent.so.4.1
>        00000f3864df5000 00000f3865254000 rlib 0    1   0      /usr/lib/libssl.so.32.0
>        00000f3875631000 00000f3875c01000 rlib 0    1   0      /usr/local/lib/libcrypto.so.33.0
>        00000f37b26f1000 00000f37b2b03000 rlib 0    2   0      /usr/lib/libpthread.so.18.1
>        00000f37ce42e000 00000f37ce91a000 rlib 0    1   0      /usr/lib/libc.so.78.1
>        00000f383d600000 00000f383d600000 rtld 0    1   0      /usr/libexec/ld.so
> $ ls -l /usr/local/lib/{libssl.*,libcrypt*}
> -rw-r--r--  1 root  wheel  12694218 Jun 15 11:47 /usr/local/lib/libcrypto.a
> -rw-r--r--  1 root  wheel       924 Jun 15 11:47 /usr/local/lib/libcrypto.la
> -rw-r--r--  1 root  wheel   6678699 Jun 15 11:47 /usr/local/lib/libcrypto.so.33.0
> -rw-r--r--  1 root  wheel   3118376 Jun 15 11:47 /usr/local/lib/libssl.a
> -rw-r--r--  1 root  wheel       934 Jun 15 11:47 /usr/local/lib/libssl.la
> -rw-r--r--  1 root  wheel   1576313 Jun 15 11:47 /usr/local/lib/libssl.so.32.0
> Any Tor devs care to shed some light on what's going on?

Can you please provide any configure or make output containing ssl or crypto?
What is the entire output in config.log for openssl configuration?

I am aware of issues in previous releases (0.2.5?) on OS X where tor would ./configure openssl based on the location of the first openssl binary in the $PATH, and not the location of the libraries or the SSL directory. I thought these had been fixed, but we might have a regression.

Is there an openssl binary in /usr/bin?
In /usr/local/bin?
What is your $PATH when ./configure is called?
What is the $PATH used in the openssl configure step? (This may require grepping logs or modifying ./configure)

There may also be an issue with the linker command generated by ./configure:

What is $LDFLAGS when ./configure is called?
What is $CC when ./configure is called?
Can you please provide the exact command-line used for linking tor, particularly any -L or -l directives? (This may require grepping logs or modifying a Makefile)

And a quick sanity check:

Does tor link entirely to /usr/lib when ./configure --with-openssl-dir=/usr is used?
What about ./configure without an --with-openssl-dir argument?

You may also find that someone on tor-dev at torproject.org is more familiar with these issues. I'm happy to take this conversation there, or cross-post, but I know that's frowned upon on some lists.


teor2345 at gmail dot com
pgp 0xABFED1AC

teor at blah dot im
OTR D5BE4EC2 255D7585 F3874930 DB130265 7C9EBBC7

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.nycbug.org/pipermail/tor-bsd/attachments/20150615/5f5b1f02/attachment.bin>

More information about the Tor-BSD mailing list