Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sat, 23 Dec 2023 03:34:58 +0000
From: Jason Keltz <>
To: "" <>
Subject: Re: 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 (0x00007ffcc79a9000) => /lib64/ (0x00007f47d421d000) => /lib64/ (0x00007f47d3d32000) => /lib64/ (0x00007f47d3a9a000) => /lib64/ (0x00007f47d3718000) => /lib64/ (0x00007f47d3500000) => /lib64/ (0x00007f47d32fc000) => /lib64/ (0x00007f47d30d3000) => /lib64/ (0x00007f47d2ec2000) => /lib64/ (0x00007f47d2c8a000) => /lib64/ (0x00007f47d2a6a000) => /lib64/ (0x00007f47d26a5000)
        /lib64/ (0x00007f47d44b1000)


From: Solar Designer <>
Sent: Friday, December 22, 2023 5:55 PM
To: <>
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).


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.