Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 22 Apr 2015 06:36:40 +0300
From: Solar Designer <solar@...nwall.com>
To: john-dev@...ts.openwall.com
Subject: Re: Johnny: core/jumbo differences

On Wed, Apr 22, 2015 at 12:08:39AM +0300, Aleksey Cherepanov wrote:
> Some ideas for all those options, not prioritized. I am not sure what
> should fall under "jumbo support" and "*2john". What options are
> needed in johnny to be not so limited for jumbo?

Primarily some sort of *2john support.  It can be an "Import" feature,
or/and it can be transparent.

Then jumbo's extra cracking modes should be available in the GUI just
like core's are.

Also, jumbo has command-line options to specify min/max password
lengths.  These should be in the GUI, too.

Johnny should detect whether it's given a core or a jumbo "john", and
show/hide (gray out?) these options accordingly.

And that's probably enough for first version.

> What are show-stoppers that prevent johnny from being used much?

I think it's primarily the way it is distributed now - only some old
version (not that there's any newer one yet) and only on the wiki.

I should probably start distributing it in the same way as I distribute
jumbo on the main Openwall website and file archive.  Alternatively, or
additionally, we may consider merging it into the jumbo tree and thus
into jumbo's distribution tarballs.  When we use autoconf anyway, we
could as well have it detect Qt and stuff, and build johnny right there.
This would boost Johnny's popularity.

> Having -fork, I'd say Johnny lacks ability to attack one file with
> several attacks at the same time, attack multiple files with one/many
> attacks (BTW john can attack several files in one invocation: like
> `john *.pw`).

Yes, being able to launch multiple attacks at once, or/and queue
multiple attacks to run one after another, would be helpful.  This does
not really depend on --fork, but it'd need to be --fork aware, so that
it would (by default) keep the total --fork=N counts for the
simultaneously launched john's no higher than a configured limit.

Similarly, it should be possible to load multiple hash files at once
(but only hashes of the same type will be attacked at once).

Alexander

Powered by blists - more mailing lists

Your e-mail address:

Powered by Openwall GNU/*/Linux - Powered by OpenVZ