Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 18 Sep 2015 01:25:49 +0300
From: Solar Designer <solar@...nwall.com>
To: john-dev@...ts.openwall.com
Subject: Re: "struct db_password" allocation

On Fri, Sep 18, 2015 at 12:13:42AM +0200, magnum wrote:
> On 2015-09-17 23:59, Solar Designer wrote:
> >On Thu, Sep 17, 2015 at 11:04:54PM +0200, magnum wrote:
> >>It's main use (or at least the reason Jim implemented it) is to get
> >>BSSID printed/logged when cracking WPA-PSK. In that case, the ESSID is
> >>the "login" and sometimes there are many same ESSID so we need to see
> >>the BSSID as well (but we do not want it used by Single mode so it can't
> >>be included in login). There might be other uses too. I'll look into
> >>that double string idea!
> >
> >Oh, I didn't realize this is controlled with ShowUIDinCracks, and is
> >disabled by default.  If so, we should simply make the allocation for
> >the uid pointer conditional upon that setting.  And no need for the
> >double string then.
> 
> I don't quite get those allocs, could you fix that please?

OK, I'll give this a try.

> Meanwhile I committed your patch, and another patch that changes some of 
> the mem buffer / --save-mem logic in wordlist mode.

Thanks.

Alexander

Powered by blists - more mailing lists

Your e-mail address:

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.