[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID:
<YTBPR01MB32782895317B8DCF09FE4684D49BA@YTBPR01MB3278.CANPRD01.PROD.OUTLOOK.COM>
Date: Sat, 23 Dec 2023 10:56:03 +0000
From: Jason Keltz <jas@...ku.ca>
To: "john-users@...ts.openwall.com" <john-users@...ts.openwall.com>
Subject: Re: john jumbo 1.9.0 and yscrypt support
I take that back. libcrypt = libxcrypt and changing the LD_LIBRARY_PATH to the newer version worked to get yescrypt support working..
Thanks again!
Jason
________________________________
From: Jason Keltz <jas@...ku.ca>
Sent: Friday, December 22, 2023 10:34 PM
To: john-users@...ts.openwall.com <john-users@...ts.openwall.com>
Subject: Re: [john-users] john jumbo 1.9.0 and yscrypt support
Hi Alexander...
The problem is that my john binary doesn't refer to libxcrypt (even though it's installed).. just refers to libcrypt.. I imagine there's a way to tell it to use libxcrypt instead of crypt?
% ldd john
linux-vdso.so.1 (0x00007ffcc79a9000)
libssl.so.1.1 => /lib64/libssl.so.1.1 (0x00007f47d421d000)
libcrypto.so.1.1 => /lib64/libcrypto.so.1.1 (0x00007f47d3d32000)
libgmp.so.10 => /lib64/libgmp.so.10 (0x00007f47d3a9a000)
libm.so.6 => /lib64/libm.so.6 (0x00007f47d3718000)
libz.so.1 => /lib64/libz.so.1 (0x00007f47d3500000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f47d32fc000)
libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00007f47d30d3000)
libbz2.so.1 => /lib64/libbz2.so.1 (0x00007f47d2ec2000)
libgomp.so.1 => /lib64/libgomp.so.1 (0x00007f47d2c8a000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f47d2a6a000)
libc.so.6 => /lib64/libc.so.6 (0x00007f47d26a5000)
/lib64/ld-linux-x86-64.so.2 (0x00007f47d44b1000)
Jason.
________________________________
From: Solar Designer <solar@...nwall.com>
Sent: Friday, December 22, 2023 5:55 PM
To: john-users@...ts.openwall.com <john-users@...ts.openwall.com>
Subject: Re: [john-users] john jumbo 1.9.0 and yscrypt support
On Fri, Dec 22, 2023 at 08:16:33PM +0000, Jason Keltz wrote:
> I compiled my own later version of libxcrypt on RHEL8, but can't seem to find an easy way to tell the compiler about it. Is there an option I can pass to configure ? Would this solve the problem ? Or not possible on RHEL8 at all?
I think the easiest way to get this working on RHEL8 would be to inject
your newer libxcrypt with LD_LIBRARY_PATH or LD_PRELOAD at the time you
invoke john. Something like:
LD_LIBRARY_PATH=~/libxcrypt/directory/with/so/file/in/it ./john ...
or similar with "export", so you don't need to specify it each time (but
then it'll affect other programs you run as well).
Alexander
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
