Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sat, 31 Dec 2011 14:27:48 +0100
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: SSE/intrinsics for sapB/sapG [was: john-users]

On 12/31/2011 04:30 AM, jfoug@....net wrote:
>> Jim, Simon, how would I do a crypt of between 56 and 63 bytes? Is this
>> not possible? Can we actually only do 0-55 *or* 64-119 bytes?
>
> To encrypt 56 bytes, do this:
>
> 1. set the 56 bytes, then set 0x80 as the 57th, and null out the rest.  Do the sha.
> 2. create another buffer. NULL the entire buffer, but put 56<<3 into the length location (last 8 bytes, BE format, I think).
> 3. perform sha on this, using the results of step 1 as the init seed.

This was almost correct. For the record, I had to put the 0x80 different:

1. first buffer: set the 56 bytes and null out the rest (neither 0x80 
nor length byte). Do the first sha.
2. second buffer: 0x80 in first byte, null the rest and put 56<<3 into 
the length location.
3. perform second sha.

magnum

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.