Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231222160721.GA4830@openwall.com>
Date: Fri, 22 Dec 2023 17:07:21 +0100
From: Solar Designer <solar@...nwall.com>
To: john-users@...ts.openwall.com
Subject: Re: john jumbo 1.9.0 and yscrypt support

Hi Jason,

On Fri, Dec 22, 2023 at 03:25:22PM +0000, Jason Keltz wrote:
> I'm trying to use John 1.9.0 jumbo with yescrypt support.
> I've compiled it on a RHEL8 system, and I know that RHEL8 doesn't use yescrypt for its own passwords, but it doesn't really matter.

Unfortunately, it does matter that RHEL8's version of libxcrypt lacks
yescrypt support.  Currently, John the Ripper only supports yescrypt via
the underlying system's crypt(3) or crypt_r(3) functions.

> The sample file I'm experimenting with has username:yescrypt hash.
> I see that there's a "yescrypt" directory inside the source folder.  I see that yescrypt is compiled as part of John.
> I can even run src/yescrypt/test and it does a bunch of successful tests!

Right, but the rest of John the Ripper jumbo tree currently only uses
that code to provide scrypt, not yescrypt.

> However, when I try to use the newly compiled john tool with yescrypt hashes, I get:
> 
> Warning: hash encoding string length 75, type id $y
> appears to be unsupported on this system; will not load such hashes.

Right.  We should indeed improve our code.  We have an open issue here:

https://github.com/openwall/john/issues/4621

For now, you need a system with newer libxcrypt, such as RHEL9 (or its
rebuilds), Fedora 29+, Ubuntu 20.04+, Debian 11+.

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.