[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090613101839.GA4287@openwall.com>
Date: Sat, 13 Jun 2009 14:18:39 +0400
From: Solar Designer <solar@...nwall.com>
To: john-users@...ts.openwall.com
Subject: Re: SHA1 salted and JTR
On Fri, Jun 12, 2009 at 06:49:40PM +0200, websiteaccess wrote:
> Benchmarking: Netscape LDAP SSHA [salted SHA-1]... DONE
> Many salts: 2056K c/s real, 2119K c/s virtual
> ------------------------------------------------------------------
> Is JTR able to crack SHA1 salted when the login is the salt ?
"Salted SHA-1" is ambiguous. There are many ways in which a salt can be
combined with a password and passed through SHA-1, and people would call
all of those hashes "salted SHA-1" or the like. So your question is not
complete. Yet I'll try to address it.
JtR with the jumbo patch supports several kinds of salted SHA-1 hashes,
with NSLDAPS_fmt.c, OPENLDAPS_fmt.c, and XSHA_fmt.c. If your salted
SHA-1 hashes process the salt and the password in the same way as one of
these, then you can get JtR to audit your hashes by converting their
encodings to the input format that these "formats" expect. As to login
names being used as salts, you'll need to encode the login names as
salts then.
A better approach could be to define a new "format", either for your
specific variation of salted SHA-1 hashes or a sufficiently generic one
to cover several common variations at once.
Alexander
--
To unsubscribe, e-mail john-users-unsubscribe@...ts.openwall.com and reply
to the automated confirmation request that will be sent to you.
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.
