[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANWtx00fqtM_L52vNjzrGjE3rScgsPhvejQhtymdzj=e+Uo-7Q@mail.gmail.com>
Date: Sun, 21 Apr 2013 09:54:14 -0400
From: Rich Rumble <richrumble@...il.com>
To: john-users@...ts.openwall.com
Subject: Re: ssha cpu format
On Sun, Apr 21, 2013 at 7:37 AM, magnum <john.magnum@...hmail.com> wrote:
> On 20 Apr, 2013, at 1:56 , Rich Rumble <richrumble@...il.com> wrote:
>
> > On Fri, Apr 19, 2013 at 7:28 PM, magnum <john.magnum@...hmail.com>
> wrote:
> >
> >> I really don't understand the question, but "salted-sha1" is the CPU
> >> format for older LDAP (corresponding to ssha-opencl for GPU). If there's
> >> newer LDAP using SHA-2, I'm not sure where we stand but it'd be a walk
> in
> >> the park to support it.
> >
> > The question is, why -format=ssha isn't available when I build it on
> windows cygwin. I've followed the instructions previously posted to the
>
> Did you mean -fo:salted-sha1 is not available on cygwin?
>
> > list: http://marc.info/?l=john-users&m=120270251402411 for extracting
> Ldap
> > hashes for an audit I'm doing.
> > My hashes look good (to me :), but aren't recognized even if I omit the
> > format switch, I may not have done something right however...
> >
> > None of these load for me (even if drop the {xxx} )
> > username:{SSHA}WTT3B9Jjr8gOt0Q7WMs9/XvukyhTQj0Ns0jMKQ==
> > username:{SHA}cMiB1KJphN3OeV9vcYF8nPRIDnk=:::::::
> > datkommadr:{SSHA}f4VgVNep4cz7Vy1BgPbmelC/N6+rYdWw7WGuLA==
> > dabob:{SSHA}sa0QU3f7p7CPpMSA3st/N9Hjjlq1in7MiIbAWw==
> > bob:{SSHA}Yio7m8PrVuK4apWV4l0TqCjbeHlvLVN6
> > data:{SHA}S0QPkjhGaP3VAe6oPukLMTh3zMmqIOJ1LlU9g==:::data
> > -rich
>
> That's strange. Here, the four {SSHA} hashes loads and cracks by the
> salted-sha1 format. One of the {SHA} hashes (the first) loads and cracks by
> the nsldap format, the other one is rejected. I'll look into why.
>
I really jumped the gun, older builds worked, and now this one does after I
recompiled, I didn't see any errors and other formats loaded so I have no
idea what I did.
I'm also not sure what to make of my result from exporting, some are
clearly md5 ($1$) and I don't know about the others...
test0:$1$senrdEPy$riZMyqYUEqeuQzYmWiccR1:::test0
test1:tvZRaa4CuWZ42CiHFB3b/VlvlFc3sVwl9O21g==:::test1
test2:+1LGSa2awMHFPvcLyT41YWT05zykGoDJ7PBoA==:::test2
test3:SXHS8VrcqsWMuQDODlBXMmh0n7+rcES:::test3
test4:$1$UBlVr6w0$TjvP9LkjCunrSkwn7GYkF1:::test4
test5:$1$fOYtADAe$yk4I2P.gezi6COlLohuck/:::test5
test6:$1$jVYt1G39$BUKCiCHw01ESckQoKu5TO1:::test6
test7:$1$jEFJgiCa$Qie3oX7XtS6b705rGsTvD/:::test7
test8:$1$a1O8i.mO$Q9Dv6JNDyC07qsvAmcXwA0:::test8
Again I apologize for not trying those hashes on previous builds and
troubleshooting further, any idea what the non-md5's are?
-rich
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.
