[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1363419372.11118.YahooMailNeo@web142301.mail.bf1.yahoo.com>
Date: Sat, 16 Mar 2013 00:36:12 -0700 (PDT)
From: "Sc00bz64@...oo.com" <sc00bz64@...oo.com>
To: "john-dev@...ts.openwall.com" <john-dev@...ts.openwall.com>
Subject: Re: Cisco - Password type 4 - SHA256
Thank you that was a fun few minutes. This is weird I feel conflicted between not releasing info and releasing info because the only reason I know about this hash is it was brought up on #hashcat because it was solved. My only advise is to just pretend you found this hash and have no clue where it came from. Now try the first two things that you should do when you find a 43 character hash with uppercase and lowercase letters, numbers, dot, and forward slash. Hmm that might be too much info. Although I don't feel douchy for not saying anything and I don't feel douchy for saying something. I win.
----- Original Message -----
From: Dhiru Kholia <dhiru.kholia@...il.com>
To: john-dev@...ts.openwall.com; "Sc00bz64@...oo.com" <sc00bz64@...oo.com>
Cc:
Sent: Friday, March 15, 2013 1:21 PM
Subject: Re: [john-dev] Cisco - Password type 4 - SHA256
On Fri, Mar 15, 2013 at 5:13 AM, Sc00bz64@...oo.com <sc00bz64@...oo.com> wrote:
> Anyone have hash examples (password:hash) of this so people can have fun with it.
Sample hashes attached. Let me know if you require more samples.
No salting is done. Some custom obfuscation?
--
Dhiru
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.
