Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOCX9Dm4ApS5me1Een+nanjF-JNQSxyVRcZPfhsD=kqBBLz2tg@mail.gmail.com>
Date: Fri, 7 Jan 2022 00:03:19 -0800
From: Lokkju Brennr <lokkju@...il.com>
To: john-users@...ts.openwall.com
Subject: Support for truncated pbkdf2-hmac-sha1 hashes?

I'm working on adding support for cracking the keys used in Chrome's Sync
system, Nigori, when a custom sync password is set. It can be converted to
a standard pbkdf2-hmac-sha1 format (with a static salt, even), except that
Nigori only uses a 16 byte hash length.

pbkdf2-hmac-sha1 seems to support variable salt lengths, but expects a 20
byte hash length, even though PBKDF2HMAC regularly supports custom hash
lengths.

Other than adding a new format, or modifying the current format, is there
any easy way to handle truncated hashes like this?

Thanks!

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.