Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 29 Dec 2011 15:15:18 -0500
From: Jordan Bradley <jordan.w.bradley@...il.com>
To: john-dev@...ts.openwall.com
Subject: Re: Making a thread safe implementation of bitslice DES

Hmm those may be of use to me, thanks. For the first one you linked you 
said it doesn't ignore DES block bits that come from the 3rd output 
character, would that mean that the third character put into the buffer 
would be incorrect? If so that won't be a problem since the first three 
characters of the result are ignored anyways. if not could you explain 
what that means a bit more plainly? I know very little about 
cryptography (as you've probably guessed).

Thanks

On 11-12-29 03:04 PM, Solar Designer wrote:
> On Sun, Dec 18, 2011 at 02:34:46PM -0500, Jordan Bradley wrote:
>> I'm writing a distributed tripcode cracking program.
> Here's what I just found:
>
> https://github.com/crypt3lx2k/BitRipper/blob/master/src/bitripper.c
>
> This attempts to reuse JtR's bitslice DES code for a tripcode cracker,
> but it looks unfinished to me.  It doesn't ignore the DES block bits
> that come from the 3rd crypt(3) output character, so should fail for 63
> out of 64 tripcodes, unless I missed something.  There may be other
> issues as well.
>
> BTW, I was not aware of this implementation when working on my
> trip_fmt.c revision a couple of days ago.
>
> Alexander
Jordan Bradley

Powered by blists - more mailing lists

Your e-mail address:

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