[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <004f01ce3af5$75b6b5f0$612421d0$@net>
Date: Tue, 16 Apr 2013 17:55:15 -0500
From: "jfoug" <jfoug@....net>
To: <john-dev@...ts.openwall.com>
Subject: RE: Bug report: specific hex salted hash failure
This patch should correct this problem.
There were parts of the salt() function and function that does the internal
salt unique code (dynamic has to do its own salt unique computations).
What this does is to ONLY adjust the salt types, IF there are supposed to be
$$2, or $$U or $$F# values in the salt. If the format does not have a use
name listed, but there is a $$U found in the salt, it should be left alone.
From: john user Sent: Tuesday, April 16, 2013 16:12
>
>also can play with these 3 byte salt values below which are an issue to me.
>
>$Uc
>$2O
>$2S
...
Download attachment "JtR_Bleeding_Dynamic_Salt2_UserID_Salt_Bug.patch" of type "application/octet-stream" (3213 bytes)
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.
