Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 13 Jul 2012 15:06:06 +0530
From: Dhiru Kholia <>
Subject: Re: RACF format

On Fri, Jul 13, 2012 at 2:26 PM, Solar Designer <> 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 ;)

> Also, it could benefit from a prepare() - to extract the username.
> Right now, the required input format is:
> userid:$racf$*userid*deshash
> whereas with prepare() you could make it simply:
> username:$RACF$hash
> and have that converted by prepare() to the representation that embeds
> the username internally (for storage in john.pot).

I didn't know about prepare(). I will check it out.

> BTW, I see no reason to have a "*" before the username.  Your code could
> instead assume that the username starts right after $RACF$ (of course,
> if this is the encoding that you'd choose to use).

Right. I have introduced this convention in lot of other formats too.
Username should start right away without the "*".


Can you please add support for RACF format in the test suite? has two implementation of
RACF hash generator (one in C and one in Python). Writing and reading
Perl is beyond me ;)


Modern RACF versions can use long (14 - 100) passphrases. It would be
great if someone could post some sample hashes.


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.