[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANO7a6x3ng=-j7MVvcMtiRt3R71RwqJZJ75oh+4-svcwceTECQ@mail.gmail.com>
Date: Mon, 20 Aug 2012 22:04:31 +0530
From: Dhiru Kholia <dhiru.kholia@...il.com>
To: john-dev@...ts.openwall.com
Subject: Re: [PATCH] Cracking MS SQL 2012 hashes
On Mon, Aug 20, 2012 at 7:39 PM, Dhiru Kholia <dhiru.kholia@...il.com> wrote:
> On Mon, Aug 20, 2012 at 12:32 PM, Dhiru Kholia <dhiru.kholia@...il.com> wrote:
>> ✗ ../run/john -fo:mssql12 -t
>> Benchmarking: MS SQL 2012 SHA512 [ms-sql12]... DONE
>> Raw: 1889K c/s real, 1889K c/s virtual
>
> I have added OMP support.
>
> ✗ ../run/john -fo:mssql12 -t
> Benchmarking: MS SQL 2012 SHA512 [ms-sql12]... (3xOMP) DONE
> Raw: 4817K c/s real, 1621K c/s virtual
>
>> I don't know much about the existing MS-SQL 05 format (which I have
>> based my code on). Can someone familiar with the code take a look?
Are set_key operations done in a bunch before crypt_all is called? I
am thinking yes.
So, the key_length should now become an array (like saved_key) for OMP
support to work correctly.
Correct?
--
Cheers,
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.
