1994-09-28 - Re: 3DES

Header Data

From: mccoy@io.com (Jim McCoy)
To: psmarie@cbis.com
Message Hash: 6798ef2bc0f10bf5b7ed528e7c13fb4c6c0e303acdf8586d5b92f5ab53554e49
Message ID: <199409282231.RAA05505@pentagon.io.com>
Reply To: <9409282126.AA00174@focis.sda.cbis.COM>
UTC Datetime: 1994-09-28 22:31:29 UTC
Raw Date: Wed, 28 Sep 94 15:31:29 PDT

Raw message

From: mccoy@io.com (Jim McCoy)
Date: Wed, 28 Sep 94 15:31:29 PDT
To: psmarie@cbis.com
Subject: Re: 3DES
In-Reply-To: <9409282126.AA00174@focis.sda.cbis.COM>
Message-ID: <199409282231.RAA05505@pentagon.io.com>
MIME-Version: 1.0
Content-Type: text/plain


> From: pstemari@bismark.cbis.com (Paul J. Ste. Marie)
> 
> Quick question.  There's a brief mention in Applied Cryptography that
> triple DES uses:
> 
> 	Eabc(x) = Ea(Db(Ec(x)))
> 
> as opposed to:
> 
> 	Eabc(x) = Ea(Eb(Ec(x)))
> 
> in order to preserve some symmetry properties.  Can anyone give a
> better explanation?

If a=b=c, a=b, or b=c  then the first operation is Ea(Da(Ea(x))) which is
just Ea(x).  This method allows one to support 56bit (single DES) and
168bit (triple DES) keys on the same function, basically making the system
backward compatible with those just using DES.

jim




Thread