Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20120227002355.GA18345@openwall.com>
Date: Mon, 27 Feb 2012 04:23:55 +0400
From: Solar Designer <solar@...nwall.com>
To: john-users@...ts.openwall.com
Subject: Re: -ext:keyboard with 8-bit chars

On Mon, Feb 27, 2012 at 12:42:09AM +0100, magnum wrote:
> On 02/26/2012 11:52 PM, Solar Designer wrote:
> > We only infer the length and id[0], but not id[1] and on (they're now
> > set to 0).  This means that when we interrupt and --restore a Keyboard
> > mode run, it tries some previously-tested candidate passwords for a
> > second time.
> 
> I don't really get the flow, but I suppose the worst-case scenario can
> be quite bad for a slow hash interrupted after a long run? If so, I
> think it's worth implementing but I have no idea how to do it.

Yes, the worst case is quite bad, but it's somewhat unlikely to be hit
and be relevant (both at the same time) in real-world usage.

Anyway, I've heard you, and I might implement this.

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.