[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <954625B4-7F03-4332-95B9-1CE8970FEB9C@patpro.net>
Date: Thu, 18 Dec 2014 08:51:55 +0100
From: patpro@...pro.net
To: john-users@...ts.openwall.com
Subject: Re: content of passwd file and --single
Hi Frank,
On 18 déc. 2014, at 08:26, Frank Dittrich <frank.dittrich@...lbox.org> wrote:
> On 12/18/2014 08:01 AM, Patrick Proniewski wrote:
>> I'm extracting account info (login, passwd...) from an LDIF file to compute a pseudo-/etc/passwd file. What fields of a regular /etc/passwd file are taken into account by --single mode?
>> We have for example a staff ID number that is sometimes used by people, I've put this number in the uid field of my processed passwd file, but I'm not sure it's the best place if I want it to be tested as password candidate.
>
> from doc/MODES:
>
>
> "Single crack" mode.
>
> This is the mode you should start cracking with. It will use the
> login names, "GECOS" / "Full Name" fields, and users' home directory
> names as candidate passwords, also with a large set of mangling rules
> applied. [...]
>
> Hope that helps.
I've read the doc before posting, but it looks kind of fuzzy to me. What I would like is an explicit list of fields that matters / where I can put pieces of info grabbed from the LDIF file. I'm not a developer, otherwise I would have read the source code.
Patrick
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.
