Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Mon, 2 Aug 2010 08:22:49 +0400
From: Solar Designer <solar@...nwall.com>
To: john-users@...ts.openwall.com
Subject: Re: John the Ripper v1.7.6 with jumbo patches, issues compiling in Solaris  {john-user discussion}

On Fri, Jul 30, 2010 at 02:20:36PM -0400, Robert Harris wrote:
> bash-3.00$ ./john
> ld.so.1: john: fatal: libcrypto.so.1.0.0: open failed: No such file or
> directory
> Killed
[...]
> bash-3.00# find / -name libcrypto.so.1.0.0
> /usr/local/ssl/lib/libcrypto.so.1.0.0
> /rob-dev/john-1.7.6-jumbo-6-MSCHAPv2-compile-old/run/libcrypto.so.1.0.0

You may invoke "john" with:

LD_LIBRARY_PATH=/usr/local/ssl/lib ./john

or:

export LD_LIBRARY_PATH=/usr/local/ssl/lib
./john

Ideally, you'd have OpenSSL installed such that these tricks would not
be needed.

Alternatively, you may use static linking.  Try adding "-static" to
LDFLAGS.  You might also have to add "-L/usr/local/ssl/lib".  Or you may
choose to only link against OpenSSL statically, but against the rest of
the libraries dynamically.  To do it, replace "-lcrypto" with
"/usr/local/ssl/lib/libcrypto.a" (or the like).

The "link against OpenSSL statically" approach is more likely to be
suitable for a binary that you'd distribute for others to use.  You'll
also need to run "ldd john" to see if there are any other library paths
specific to your system (rather than to Solaris in general).  If so,
deal with those as well.

Thanks,

Alexander

Powered by blists - more mailing lists

Your e-mail address:

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.