Re: Proposed Up/Down protocol description

[Robert Loomans <robertl@apnic.net>]

> BUT if the Signing Time attribute of the CMS wrapper is NOT protected by
> the CMS digital signature then my assumption is _not_ valid (!)
> 
> ***Does anyone want to confirm that the digital signature of CMS covers
> the Signing Time attribute?

In RFC 3852, section 11.3:

   The signing-time attribute MUST be a signed attribute or an
   authenticated attribute; it MUST NOT be an unsigned attribute,
   unauthenticated attribute, or unprotected attribute.



-- 
Robert Loomans                                 Email:  robertl@apnic.net
Programmer/Analyst, APNIC                      Phone:    +61 7 3858 3100
http://www.apnic.net                             Fax:    +61 7 3858 3199

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature