[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 24 May 2012 16:03:31 -0500
From: "jfoug" <jfoug@....net>
To: <john-dev@...ts.openwall.com>
Subject: RE: memory usage within JtR and possible ways to significantly reduce it.
>From: Solar Designer [mailto:solar@...nwall.com]
>
>> I ... am
>> looking at starting on the 'optional' source() method, to eliminate
>> having to have the hashes allocated (IF a format can recreate the
>> hash, some may not be able to do that)?
>
>Please feel free to experiment with that if you like.
I will start looking at this. I do think legacy formats should maintain
existing behavior, and formats themselves would 'tell' JtR, through
implementation of that source() function, that they are able to process
properly without the call to cmp_exact, and will be able to reconstruct the
hash from the call source, thus JtR core does not have to store it.
I will work on getting this done on dynamic, and probably NT. Once it
works, and we can regression test and also regression to make sure no
performance is lost, then we can see if other formats can be re-worked to
get this to work.
Alex, as long as you are OK with the interface { char *source(void
*bin_hash, void *salt), or possibly char *source(void *bin_hash, void *salt,
char Buffer[LINE_BUFFER_SIZE]), so that this function is thread safe },
then I will not bother you with it again, until it is done, and even then,
there will be nothing to do, until you look at putting it in permanently in
1.8
Jim.
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.
