Date: Wed, 13 Mar 2013 05:11:19 +0400 From: Solar Designer <solar@...nwall.com> To: john-dev@...ts.openwall.com Subject: Re: formats that duplicate dynamics Dhiru, magnum - what's the status on the below. This is a blocker for making a new jumbo release. On Sun, Jan 27, 2013 at 07:11:50AM +0400, Solar Designer wrote: > On Sun, Jan 27, 2013 at 08:31:11AM +0530, Dhiru Kholia wrote: > > On Sun, Jan 27, 2013 at 8:05 AM, Solar Designer <solar@...nwall.com> wrote: > > > > > > The "postgre" format at the very least needs to be renamed from the > > > ridiculous "postgre" to "postgres". This includes the filename, > > > FORMAT_LABEL, and the "$postgre$" prefix string. > > > > If these changes are final, they will also involve sending a small > > patch to Ettercap project. > > Unless anyone suggests a different kind of rename/action (and we agree > on that), yes - we'll likely end up making the above changes. > > It is possible that the prefix string will need to be changed to a > $dynamic_*$, though. > > > Do you want to do these changes before the upcoming release? > > Definitely. > > > > However, there's a more general issue: can't the same be implemented as > > > a dynamic format? > > > This general issue probably applies to several other formats as well, > > > including e.g. "mongodb". > > > > I promised to use dynamic format where I could and I did > > (htdigest2john.py is an example). > > In those cases, we should also be documenting those dynamics prominently > as being usable for the well-known things that they can be used to crack. > This includes setting their names visible in --test accordingly. > > > I will see if the above mentioned formats can be implemented using > > dynamic format. > > OK. Thanks! > > Alexander
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.