Encrypting the MIC-Info field?

David Rudder <drig@magicweb.com> Fri, 06 September 1996 18:31 UTC

Received: from ietf.org by ietf.org id aa12181; 6 Sep 96 14:31 EDT
Received: from cnri by ietf.org id aa12177; 6 Sep 96 14:31 EDT
Received: from neptune.hq.tis.com by CNRI.Reston.VA.US id aa12954; 6 Sep 96 14:31 EDT
Received: from neptune.tis.com by neptune.TIS.COM id aa06457; 6 Sep 96 13:58 EDT
Received: from relay.hq.tis.com by neptune.TIS.COM id aa06429; 6 Sep 96 13:52 EDT
Received: by relay.hq.tis.com; id NAA00432; Fri, 6 Sep 1996 13:55:48 -0400
Received: from sol.hq.tis.com(10.33.1.100) by relay.tis.com via smap (V3.1.1) id xmaa00424; Fri, 6 Sep 96 13:55:30 -0400
Received: from relay.hq.tis.com by tis.com (4.1/SUN-5.64) id AA12860; Fri, 6 Sep 96 13:54:39 EDT
Received: by relay.hq.tis.com; id NAA00409; Fri, 6 Sep 1996 13:55:20 -0400
Received: from ws5.magicweb.com(207.88.92.102) by relay.tis.com via smap (V3.1.1) id xma000390; Fri, 6 Sep 96 13:54:57 -0400
Received: (from drig@localhost) by drig.magicweb.com (8.6.12/8.6.9) id KAA01931; Fri, 6 Sep 1996 10:56:32 -0700
Date: Fri, 06 Sep 1996 10:56:30 -0700
Sender: ietf-archive-request@ietf.org
From: David Rudder <drig@magicweb.com>
To: pem-dev@tis.com
Subject: Encrypting the MIC-Info field?
Message-Id: <Pine.LNX.3.91.960906104940.1915A-100000@drig.magicweb.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
X-Orig-Sender: pem-dev-approval@neptune.tis.com
Precedence: bulk

Hello,
	I was wondering if anyone could help me with the MIC-Info and
Key-Info fields.  The application I'm writing does not decrypt RIPEM 
correctly.  The problem lies in both of these fields.

	Basically, I'm working on the assumption that to encrypt these 
fields, you just 
a) make the DEK (8 byte array for DES-CBC)
b) encrypt using the recipient's public key
c) print it as ascii encoded HEX values

But, RFC1423 seems to say that you 
a) make the DEK
b) encode it with  0x00 || BT || PS || 0x00 || D
                          0x02   random        dek
c) encrypt it sing the recipient's public key
d) print it out

or, b and c might be switched

But, RIPEM doesn't seem to work with any of these.  Do I have to break up 
the DEK into smaller chunks first?  I'M CONFUSED!!!!!! (and just a little 
bit frustrated).  

		Thanks in advance,

	 Your confused new-born cypherpunk-wannabe,
			Dave
		   drig@magicweb.com

I got a coffee mug from Cray Research when they moved out.  Now I can 
drink my coffee while doing 63 other, unrelated tasks.