[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <04af01cd60fc$2c10b550$84321ff0$@net>
Date: Fri, 13 Jul 2012 08:34:03 -0500
From: "jfoug" <jfoug@....net>
To: <john-dev@...ts.openwall.com>
Subject: RE: RACF format
This actually could be a good 'get your feet wet' type task for someone that
is wanting to get started learning about hacking into JtR coding, i.e. some
eager new up/comer coder. Is there anyone like this who has shown interest,
but has yet to start?
On 07/13/2012 5:08 AM Frank Dittrich wrote:
>On 07/13/2012 11:46 AM, Solar Designer wrote:
>> On Fri, Jul 13, 2012 at 03:06:06PM +0530, Dhiru Kholia wrote:
>>> On Fri, Jul 13, 2012 at 2:26 PM, Solar Designer <solar@...nwall.com>
>wrote:
>>>> racf_fmt_plug.c needs a proper valid(), not just a check for $racf$.
>>>
>>> This problems exists in lot of my formats. I am secretly waiting for
>>> Frank to send the patches ;)
>>
>> Don't wait. Patch.
>
>Right. I am too busy with other things.
>If I had time, I would prefer to add new/enhanced functionality.
>
>One other format which still needs an improved valid() is episerver
>(looks like the inappropriate name will stay).
>episerver_fmt.c's valid() also just contains return !strncmp(ciphertext,
>"$episerver$", 11);
>
>Almost everything you find using
>
>grep -C 2 "return\s*\!strncmp(ciphertext" *.c
>
>(except dynamic_fmt.c) needs to be fixed
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.
