1996-10-18 - Re: DES cracker.

Header Data

From: Adam Back <aba@dcs.ex.ac.uk>
To: sameer@c2.org
Message Hash: 816de0c5344fd978cb3b934a25a3a9626187c5cb93adc137b48c43ce00b72379
Message ID: <199610171530.QAA00463@server.test.net>
Reply To: <199610162058.NAA06263@clotho.c2.org>
UTC Datetime: 1996-10-18 00:36:49 UTC
Raw Date: Thu, 17 Oct 1996 17:36:49 -0700 (PDT)

Raw message

From: Adam Back <aba@dcs.ex.ac.uk>
Date: Thu, 17 Oct 1996 17:36:49 -0700 (PDT)
To: sameer@c2.org
Subject: Re: DES cracker.
In-Reply-To: <199610162058.NAA06263@clotho.c2.org>
Message-ID: <199610171530.QAA00463@server.test.net>
MIME-Version: 1.0
Content-Type: text/plain



[added cc cypherpunks also]

Sameer Parekh <sameer@c2.org> writes:
> Peter Trei <trei@process.com> writes:
> > 	Ideally, this should be a DEMO case of a real world encrypted
> > application, in which we have a cryptotext, and a known plaintext,
> > each at least one 8-byte block long.
> 
> 	I'd like to get in touch with a bank who can provide us some
> sample ciphertext for an ATM transaction or something like that. I
> initially thought we should hit SWIFT, but that would be very
> illegal. =)

If someone can dig up a selection of banking protocols (some of these
things must be standardised), perhaps we can simulate the same thing
without the legal implications.

Of course you'd need the person constructing the challenge to be
trustworthy to the tune of $10k, or whatever the prize fund pans out
to be.  For that matter the NSA, or anyone else with a hardware
breaker would be able to cheat, but then they help our cause, which is
to demonstrate how weak DES is :-)

So start digging for banking protocols!  Personal contacts, web
searches, obtaining standard documents, dumpster diving, whatever it
takes.

Adam
--
print pack"C*",split/\D+/,`echo "16iII*o\U@{$/=$z;[(pop,pop,unpack"H*",<>
)]}\EsMsKsN0[lN*1lK[d2%Sa2/d0<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<J]dsJxp"|dc`





Thread