[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAEDDmE2r-LD+VE1M+u5kRm3scdhyC=xakWV-rcfk=h69T=ns+A@mail.gmail.com>
Date: Sat, 9 Jun 2018 23:41:44 -0400
From: Chris Bonk <bonk.chris@...il.com>
To: john-users@...ts.openwall.com
Cc: magnum <john.magnum@...hmail.com>
Subject: Re: Using PBKDF2-HMAC-SHA256
Chiming back in.
I solved the issue. I made the mistake of base64 encoding literally the hex
string.
@jfoug is correct.
I needed to modify the derivation and salt to be encoding to base64 from
binary.
I ended up using hashcat, which is currently running.
I hope this helps anyone else if they encounter similar issues.
CB
On Sat, 9 Jun 2018 at 23:16 jfoug <jfoug@...nwall.net> wrote:
> On 6/9/2018 6:40 PM, magnum wrote:
> > That's valid data for sure, but it's 44 bytes and that hash doesn't
> > load - I have no idea why. I believe JimF wrote the current
> > incarnation of the format.
> AFAIK, the input string was an ITW format, and thus processed as it is.
> I was provided the input hashes, and wrote the format to use them. Why
> they are the way they are, I can not say for sure.
>
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.
