[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <538bbe629fbb0c7070f068789da9d52f@smtp.hushmail.com>
Date: Sat, 5 Jan 2013 01:29:25 +0100
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: New plugin load order magic
On 5 Jan, 2013, at 1:10 , magnum <john.magnum@...hmail.com> wrote:
> After Lukas' struct name fixes, I opted to try the struct-name sort order, committed now. I took the chance to rename fmt_rawSHA512 to fmt_raw0_SHA512 which ensures it loads before the Blake2 format.
Here's another thought:
All GPU formats are non-plugs, so load order is chosen manually in john.c. I think we should register them before all plugins and maybe even before the core formats. This means:
- If you have a GPU build and load crypt-md5 hashes without giving --format, the GPU format will load.
- If we register even before core, NT-opencl will take precedence not only before CPU NT, but also before the LM format.
Thoughts? I can see this is arguable. However, registering eg. wpapsk-opencl before the cpu version is a no-brainer, so I will do some of those if nothing else.
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.
