Nelson B wrote: >Michiel > >The old SEC_PKCS7 API is deprecated. It conforms to the original PKCS#7, >not to the newer "Cryptographic Message Syntax" RFC which superseded PKSC#7 >and is a superset of PKCS#7. > >NSS has a newer library that implements the newer RFC. IMO, all new >development should be using it instead of the old SEC_PKCS7 API. > >It's called libSMIME (which is a misnomer, because it doesn't do any MIME). >There is a test program for it, cmsutil. >I suggest that you see if you can get cmsutil to decrypt your message. > > > cmsutil gives me the following output:
: cmsutil -D -i envelopeddata.dat -o signeddata.dat -v received commands NSS has been initialized. Got default certdb cmsutil: failed to decode message. cmsutil: problem decoding: security library: invalid algorithm. Which is what I expected, as the encoding algorithm used is unknown to NSS unless I add it myself. I did try to decode the structure using the CMS routines, but they also give me the exact same garbled output... Not a signeddata structure as I would have expected, but the same output never the less... So I expect this is a lower level problem (not the API used), I just can't find out what it is. Michiel __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
