[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Authenticated Data Content Type

To: ietf-smime <ietf-smime@xxxxxxx>
Subject: Authenticated Data Content Type
From: Vamsi Motukuru <vamsi@xxxxxxxxx>
Date: Fri, 12 Jan 2001 16:47:11 -0500
In-reply-to: <>
List-archive: <http://www.imc.org/ietf-smime/mail-archive/>
List-id: <ietf-smime.imc.org>
List-unsubscribe: <mailto:ietf-smime-request@imc.org?body=unsubscribe>
Sender: owner-ietf-smime@xxxxxxxxxxxx

All,

My question is concerning the CMS authenticated data type.

RFC2104 allows the HMAC key to be of any length. If this is the case, then the KEKRecipientInfo can not be used to transfer the Recipient Info unless the length of the authentication key matches that of a Triple-DES or RC2 Key as this is required by the Key Wrap Algorithms.

Thanks,
 Vamsi

Follow-Ups:
- Re: Authenticated Data Content Type
  - From: Russ Housley

References:
- RE: S/MIME signed attributes
  - From: Pawling, John

Prev by Date: Cyber Success Secrets
Next by Date: Re: Authenticated Data Content Type
Previous by thread: RE: S/MIME signed attributes
Next by thread: Re: Authenticated Data Content Type
Index(es):
- Date
- Thread