[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4d9132cbd72debde17f1500c297728b4@smtp.hushmail.com>
Date: Sun, 17 Mar 2013 18:58:13 +0100
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: Cisco - Password type 4 - SHA256
On 17 Mar, 2013, at 16:39 , Dhiru Kholia <dhiru.kholia@...il.com> wrote:
> On Sun, Mar 17, 2013 at 6:49 PM, magnum <john.magnum@...hmail.com> wrote:
>> Is this ready for committing to bleeding? Perhaps we should even include it (as well as the CPU format) in Jumbo-8?
>
> I am currently *not* in favour of introducing new format(s) for
> cracking Cisco "type 4" hashes (future code maintenance problems?).
>
> I think that existing format(s) and the new cisco2john.pl utility are
> enough for cracking Cisco "type 4" hashes.
>
> cisco2john.pl can be found at
> https://github.com/kholia/JohnTheRipper/blob/cisco-type-4/run/cisco2john.pl
>
> magnum,
>
> Do you think that introducing new specific format(s) has any
> advantages over this mentioned approach?
No, I was confused. I think the existing formats (CPU and GPU) should be modified to accept Cisco hashes without pre-parsing.
We should commit cisco2john.pl to unstable, and introduce support for native Cisco hashes in bleeding only.
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.
