[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <030e01cd3d29$2e52e370$8af8aa50$@net>
Date: Mon, 28 May 2012 18:25:33 -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]
>
>Makes sense. This choice (re-purpose bleeding-jumbo vs. create
>testing-jumbo) is up to you. I just want the main magnum-jumbo to stay
>without this stuff for now.
When we cut this out, I am going to make a patch and place it into the wiki.
In that patch, I will not make changes to all of the formats, putting the
fmt_default_get_source into each format. I will simply leave it out, and
make a change to the format init code within john.c, so that if that method
is NULL, that the code will properly setup that pointer, after the init of
the format.
>BTW, a related issue is that we're breaking the dynamic plugins with
>this change. At the very least we need to bump up the id number, so
>that we break the one existing plugin in a more graceful fashion. %-)
I do not fully agree. The change was done as an optional flag. IF that
flag was seen in john.conf, and run using an older JtR, then there should be
no problem. JtR would operate just fine. Of course it would not have or
use the get_source.
I do not remember putting a version ID into the dynamic format, but if we
did, I will look into it. I do not see this as breaking anything, however.
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.
