[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 12 Dec 2011 09:27:14 -0600
From: "jfoug" <jfoug@....net>
To: <john-dev@...ts.openwall.com>
Subject: RE: cracking RADIUS shared secrets with john the ripper
I have fixed johnswap.h It was not only an OSX thing, it was any build,
other than gcc 4.3+, linux, or vc. As for the #if __linux__ block,
should we change that to #if __GCC__ ?? There was also a problem with
dynamic_fmt.c, where there were a couple of multiple defined junk, if the
build was not one of the first 3 'types'. Pretty simple fix there. Simply
remove the ROTATE_LEFT macros (they are defined in johnswap)
I will get the changes made to dynamic to validate the HEX$ soon, hopefully
this morning still.
Jim.
>-----Original Message-----
>From: magnum [mailto:john.magnum@...hmail.com]
>Sent: Sunday, December 11, 2011 7:44 AM
>To: john-dev@...ts.openwall.com
>Subject: Re: [john-dev] cracking RADIUS shared secrets with john the
>ripper
>
>2011-12-10 00:23, Didier Arenzana wrote:
>> On Fri, Dec 9, 2011 at 7:52 PM, jfoug <jfoug@....net> wrote:
>>> It has been posted as patch 0043- the salt() function now does all
>of the
>>> work, including figuring out what salts are identical. Dynamic
>returns 4
>>> byte or 8 byte 'salts' back to john, which will always be unique.
>These 4
>>> or 8 bytes are simply the data contents of a pointer.
>>
>> I have donwloaded and built the patch, and you will find attached a
>> patch on top of this one, that contains the following modifications:
>...
>
>I just posted a patch 0044 containing radius2john.pl and the dynamic
>config (versions currently on
>http://openwall.info/wiki/john/Using-john-to-crack-RADIUS-shared-
>secrets).
>I did not add the above mentioned modifications to dynamic_fmt, I'll
>leave that to Jim. This johnswap.h vs OSX thing was unexpected, good
>thing it was caught now.
>
>magnum
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.
