Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 20 Dec 2011 11:31:08 +0530
From: piyush mittal <piyush.cse29@...il.com>
To: john-dev@...ts.openwall.com
Subject: Re: Bit slice implementation of DES based hashes

Can I switch to NTLM hash that is almost similar to LM ?Remaining part of
oracle we can do later....Because I have just one week left for my
holidays.In between that I can complete at least this.

Thanks.

On Tue, Dec 20, 2011 at 8:16 AM, piyush mittal <piyush.cse29@...il.com>wrote:

> Hi,
>
> Implementation is completed and I have used Unicodes as well and that is
> working fine but I am getting self test failed this is because the
> implementation is not fully correct.The crypt function of LM on which this
> implem. is based upon have ECB mode.but in oracle we need CBC, so we have
> not used any initialisation vector concept.Also I have initialised B in
> following way before calling DES_bs_crypt_LM()  (I have removed B
> initialization(i.e DES_bs_set_block_8()) in this function).
>
>
>
> char *plain_salt_mix=utf16_to_utf8(cur_salt); //cur_salt is a combination
> of (username+password) in UTF 16
> length=strlen(plain_salt_mix);
>
> *
> *for(i=0;i<length;i++)
> DES_bs_all.B[i][0]=plain_salt_mix[i];
>
> for(j=i;i<64-length;i++)
> DES_bs_all.B[i][0]=0;
>
> Is this correct?
>
> Thanks,
>
>
>
>
>
>
> On Sun, Dec 18, 2011 at 11:03 PM, piyush mittal <piyush.cse29@...il.com>wrote:
>
>> Correct sequence is
>>
>> 00000000
>> 00010001
>> 00100010
>> 00110011
>> 01000100
>> 01010101
>> 01100110
>> 01110111
>>
>> And you are extremely right.String will be
>> "\x80\x11\x22\x33\x44\x55\x66\x77"
>>
>> Thanks a lot.
>>
>> On Sun, Dec 18, 2011 at 8:37 PM, Solar Designer <solar@...nwall.com>wrote:
>>
>>> On Sun, Dec 18, 2011 at 08:22:35PM +0530, piyush mittal wrote:
>>> > Even if I drops the parity bits then remaining 56 bits are as follows
>>> >
>>> > 00000000010001010001001100111000100101010111001101110111
>>> >
>>> > and its corresponding  ASCII equivalent I am not getting.
>>>
>>> I did not verify the above binary value (in fact, it looks wrong to me),
>>> but I see no problem in converting it to an ASCII equivalent for
>>> DES_bs_set_key() or DES_bs_set_key_LM() (these ASCII strings would be
>>> different).  In fact, I already posted it for DES_bs_set_key():
>>>
>>> > > "\x80\x11\x22\x33\x44\x55\x66\x77"
>>>
>>> Alexander
>>>
>>
>>
>>
>> --
>> Piyush Mittal
>> Department of Computer Science and Engineering
>> National Institute of Technology,Rourkela
>> INDIA
>>
>>
>>
>
>
> --
> Piyush Mittal
> Department of Computer Science and Engineering
> National Institute of Technology,Rourkela
> INDIA
>
>
>


-- 
Piyush Mittal
Department of Computer Science and Engineering
National Institute of Technology,Rourkela
INDIA

Content of type "text/html" skipped

Powered by blists - more mailing lists

Your e-mail address:

Powered by Openwall GNU/*/Linux - Powered by OpenVZ