Date: Sun, 06 Apr 2014 22:57:01 +0200 From: magnum <john.magnum@...hmail.com> To: john-dev@...ts.openwall.com Subject: Re: RFC on format alias coding On 2014-04-05 16:04, jfoug@....net wrote: > The biggest question I have, is what would people implementation > details be. I can think of things like this: > 1. alias's would be handled in a stand alone file (possibly a .conf > included by john.conf). > 2. the alias engine would need to load all formats listed in this config file. > 3. I believe that prepare()/valid() can be called prior to init, so > the alias would not need to init the formats (hopefully). > 4. at proper points within JtR coding (mostly loading, etc), calls > would be made to the alias engine, to see if a hash matches one of > the alias's for the currently being used format. Having the aliases in john.conf sounds like a good idea. I'm trying to recall different use cases. We have things like MD5 vs. dynamic_0, and NT vs dynamic_33 but these are no different from what you are doing now. I can't remember any "different" situation right now. 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.