|
Message-ID: <DUB127-W33203A4E25615FC30C05E2CFFA0@phx.gbl> Date: Sat, 16 Nov 2013 20:44:21 +0200 From: Yazar Oku <yazaroku2013@...mail.com> To: "john-users@...ts.openwall.com" <john-users@...ts.openwall.com> Subject: RE: {crypt} unsupported Hi, Thank you for the quick replies. After removing the {crypt} part, John managed to detect the method (The {SSHA} is automatically detected, so I didn't remove it). I have kept the "username@...ain" parts as the reporting is important. I have also separated the two hash types on different files so that John can deal with each of them. Now, two John instances are running. With the help of "OMP_NUM_THREADS" I am able to benefit from the multiple cores but only when dealing with {crypt} hashes. When dealing with {SSHA}, htop shows only a single core reaching 100%. The rest of the cores are sitting idle. Any idea ? > Date: Sat, 16 Nov 2013 21:37:27 +0400 > From: solar@...nwall.com > To: john-users@...ts.openwall.com > Subject: Re: [john-users] {crypt} unsupported > > Yazar - > > > On 11/16/13 at 09:36am, Yazar Oku wrote: > > > A sample hash is below ; > > > username@...ain:{crypt}$1$8ebe5e6d$cY6OomZFrbA5ljt3e7.Ql. > > To crack these hashes, remove the "{crypt}" portion of each line, e.g. > with: > > sed 's/{crypt}//' < inputfile > outputfile > > Also, for greater performance, build your JtR with OpenMP enabled. > These are md5crypt hashes, and for them OpenMP support is quite efficient. > > On Sat, Nov 16, 2013 at 10:54:28PM +0530, Dhiru Kholia wrote: > > Can you try removing the "username@...ain:{crypt}" part from the hashes? > > I think it's best to preserve the "username@...ain:" part. It may > result in more passwords cracked due to "single crack" mode extracting > and making use of this info, and it will provide better reporting. > > Alexander
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.