John:
>3) Sec 3.2 specifies that the md5WithRSAEncryption or sha1WithRSAEncryption
>OID should be used in the signerInfo signatureAlgorithm field instead of
the
>id-rsaEncryption OID. I agree with this strategy, but please note that
this
>is a change from what is specified in RFC 2630. RFC2630 specifies the use
>of id-rsaEncryption in the signerInfo signatureAlgorithm field. Is this
>change going to cause backwards compatibility problems with legacy CMS
>implementations?
I want to highlight this point. As you say, it might be controversial. I
will start a thread to discuss this point.
[JSP: I already started a separate thread.]
Me too....
Russ