[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sat, 3 Dec 2011 20:09:21 +0530
From: piyush mittal <piyush.cse29@...il.com>
To: john-dev@...ts.openwall.com
Subject: Re: Bit slice implementation of DES based hashes
>
> This is a subset of them. There are several more. Here they are, by
> filename in 1.7.8-jumbo-8 (including the above):
>
> AFS_fmt.c
> KRB4_fmt_plug.c
> KRB5_fmt_plug.c
> MSCHAPv2_fmt_plug.c
> NETLM_fmt_plug.c
> NETNTLM_fmt_plug.c
> NETSPLITLM_fmt_plug.c
> oracle_fmt_plug.c
> trip_fmt_plug.c
>
> Of these, AFS_fmt.c and trip_fmt_plug.c currently use John the Ripper's
> own non-bitslice DES code, whereas the rest use OpenSSL's.
>
>
Ok.Actually i was searching based on their label only.But all of them that
you mentioned above are using openssl/des header files(i.e based on DES).
What's your reason to start with this one? Is this arbitrary choice?
>
> For optimal performance, trip_fmt_plug.c and AFS_fmt.c would need to
> buffer larger numbers of candidate passwords (way beyond DES_BS_DEPTH
> per thread) and group them by certain criteria. For the rest, this is
> probably not needed.
>
Yes that was my arbitrary choice.And today learn a lot about trip codes.If
above mentioned complexities are there in this format.I will do it later.
MSCHAPv2_fmt_plug.c
> NETLM_fmt_plug.c
> NETNTLM_fmt_plug.c
> NETSPLITLM_fmt_plug.c
> oracle_fmt_plug.c
>
To work on Oracle hashes will be more interesting so i am going to start
with it.But i need a proper algo about how hashes are designed in it using
DES because just following directly code is bit complicated for me.I just
got this information.
Up to 30 characters long. All characters will be converted to uppercase
> before the hashing starts
> 8-byte hash, encrypted with a DES encryption algorithm without real salt
> (just the username).
>
Thanking you.
On Sat, Dec 3, 2011 at 3:34 PM, Solar Designer <solar@...nwall.com> wrote:
> On Sat, Dec 03, 2011 at 02:15:50PM +0530, piyush mittal wrote:
> > How to run Jtr is not a big issue.I don't know what was the problem
> > with "john-1.7.8-jumbo-7" on my 64 bit platform.Right now i am working
> > with "john-1.7.8-jumbo-8" and that is working fine.
>
> OK. Maybe you forgot a "make clean" between builds or something.
>
> > After enumerating through all Des based formats.I got following
> > formats that are not using bilt slicing concept
> >
> > Tripcode DES
> > Half LM C/R DES
> > LM C/R DES
> > NTLM v1 C/R MD4 DES
>
> This is a subset of them. There are several more. Here they are, by
> filename in 1.7.8-jumbo-8 (including the above):
>
> AFS_fmt.c
> KRB4_fmt_plug.c
> KRB5_fmt_plug.c
> MSCHAPv2_fmt_plug.c
> NETLM_fmt_plug.c
> NETNTLM_fmt_plug.c
> NETSPLITLM_fmt_plug.c
> oracle_fmt_plug.c
> trip_fmt_plug.c
>
> Of these, AFS_fmt.c and trip_fmt_plug.c currently use John the Ripper's
> own non-bitslice DES code, whereas the rest use OpenSSL's.
>
> > I will try to convert Tripcode DES first.
>
> What's your reason to start with this one? Is this arbitrary choice?
>
> For optimal performance, trip_fmt_plug.c and AFS_fmt.c would need to
> buffer larger numbers of candidate passwords (way beyond DES_BS_DEPTH
> per thread) and group them by certain criteria. For the rest, this is
> probably not needed.
>
> You could want to start with any one of these:
>
> MSCHAPv2_fmt_plug.c
> NETLM_fmt_plug.c
> NETNTLM_fmt_plug.c
> NETSPLITLM_fmt_plug.c
> oracle_fmt_plug.c
>
> If successful, then proceed with the remaining 4 of them. After that,
> proceed with:
>
> trip_fmt_plug.c
> AFS_fmt.c
>
> And finally approach the arguably outdated ones (hence less important):
>
> KRB4_fmt_plug.c
> KRB5_fmt_plug.c
>
> That's just a suggestion.
>
> Thanks,
>
> Alexander
>
--
Piyush Mittal
M.Tech SEM-Ist
Department of Computer Science and Engineering
National Institute of Technology,Rourkela
INDIA
Email. piyush.cse29@...il.com
211cs2281@...rkl.ac.in
Mob. +91 8260859399
Content of type "text/html" skipped
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.
