Subject: message-digest attribute in signed data

From: [email-masked]
Date: Wed, 16 Oct 2002 12:11:35 +0200

In RFC 2630 "Cryptographic message syntax", a message-digest attribute is defined as being the digest of the encapContentInfo eContent OCTET STRING being signed in signed-data. For signed-data, the same RFC requires that message-digest attribute be present as a signed attribute if any attributes are added. So i understand that it is easier for a signature verification application to have the message-digest added as a signed attribute since it shouldn't hence care about the order of the signed attributes, but are there any other particular reasons to put the message-digest attribute as a signed attribute? 

Regards,

malek bechlaghem.

**** DISCLAIMER **** 
"This e-mail and any attachments thereto may contain information 
which is confidential and/or protected by intellectual property 
rights and are intended for the sole use of the recipient(s) named above. 
Any use of the information contained herein (including, but not limited to, 
total or partial reproduction, communication or distribution in any form) 
by persons other than the designated recipient(s) is prohibited. 
If you have received this e-mail in error, please notify the sender either 
by telephone or by e-mail and delete the material from any computer. 
Thank you for your cooperation."