[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <982f7fe1f80e87c657135c7af8731353@smtp.hushmail.com>
Date: Sat, 8 Dec 2012 13:08:47 +0100
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: rc4-hmac parsing support + etype 17 + input format unification (Was: Re: [john-users] support for weak kerberos etypes)
On 8 Dec, 2012, at 5:43 , Dhiru Kholia <dhiru.kholia@...il.com> wrote:
> On Sat, Dec 8, 2012 at 9:49 AM, Dhiru Kholia <dhiru.kholia@...il.com> wrote:
>> If we decide to drop "salt type" field, then how are you planning to
>> parse the "ciphertext"? strtok will jump to next field (user)
>> automatically. "salt type" field is helping us know if we have M$ AD
>> style salt available.
>>
>> Always figuring out user and realm fields is not easy (at least with
>> the current parser) when M$ AD is involved.
>
> For now, I have kept the "salt type" field.
We leave unknown/unused fields empty, ie. ...$$... - I don't see the problem?
> Done in commit 6aa836b442c2b089d9850e3be31fdba03507102f
Great, I'll pick up from there.
magnum
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.
