Re: Correct definition of ContentInfo in CMS-10

Peter,

When using detached signatures, I agree that the eContent is absent, but the
content is still required to convey the SignedData and hence the signature.
-----Original Message-----
From: Peter Gutmann <pgut001(_at_)cs(_dot_)aucKland(_dot_)ac(_dot_)nz>
To: ietf-smime(_at_)imc(_dot_)org <ietf-smime(_at_)imc(_dot_)org>; 
ross(_at_)jgross(_dot_)demon(_dot_)co(_dot_)uk
<ross(_at_)jgross(_dot_)demon(_dot_)co(_dot_)uk>
Date: Monday, February 22, 1999 3:04 PM
Subject: Re: Correct definition of ContentInfo in CMS-10


> > > Within the body of CMS 10 ContentInfo is defined as : -
> > >
> > > ContentInfo ::= SEQUENCE {
> > >        contentType ContentType,
> > >        content [0] EXPLICIT ANY DEFINED BY contentType }
> > >
> > > However, in the appendix ContentInfo is defined as : -
> > >
> > > ContentInfo ::= SEQUENCE {
> > >     contentType ContentType,
> > >     content [0] EXPLICIT ANY DEFINED BY contentType OPTIONAL }
> > >
> > > I assume the one within the body (i.e. content not optional) is correct.
> > I assume that content is not optional
> The content is optional.  Think about how detached sigs work.
>
> Peter.