[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <3927F8E4-9A76-46B0-B598-E4EE6948D652@shinnok.com>
Date: Fri, 24 Jul 2015 17:35:53 +0300
From: Shinnok <admin@...nnok.com>
To: john-dev@...ts.openwall.com
Subject: Re: Default attack format
> On Jul 23, 2015, at 8:14 PM, Mathieu Laprise <mathlaprise@...il.com> wrote:
>
> On Thu, Jul 23, 2015 at 4:51 AM, Shinnok <admin@...nnok.com <mailto:admin@...nnok.com>> wrote:
>
> Let's implement the core approach for this sprint and add a new feature issue on Github for the jumbo approach and assign to the next sprint.
>
> Use magnum's approach , `john -stdin hashfile <<< ""` , if it is the minimal overhead one.
>
> All right, I'll do this. As I understand it, the core approach from magnum works with jumbo too, right ? If this approach works for core and jumbo, why would we implement in next sprint both approach ?
>
Well, partly because I like the approach that yields the results in the most usable fashion and partly because it is the least impact approach. We already call show formats via the HashTypeChecker handler, so it would be just a matter of adding a couple more lines to support this for Jumbo and not start an attack just to get that piece of info. I guess it sums up to being technically elegant, even if just for Jumbo.
I added the task for sprint 2.3 which would be mostly jumbo work.
Shinnok
Content of type "text/html" skipped
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.
