On 31/03/2010 17:11, Kaspar Brand wrote:
On 31.03.2010 07:49, Michael Ströder wrote:
It seems it's a CMS structure and recipientInfos contains subject key ids
instead of issuerAndSerialNumber. It seems Seamonkey 2.0.x does not support
that. Is it supported by the underlying libs?
I believe so, see
http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/security/nss/lib/smime/cmsreclist.c&mark=89-91#85
That's the code which is used by nsCMSMessage
(http://mxr.mozilla.org/comm-central/ident?i=nsCMSMessage), and
therefore also by Seamonkey.
Are you certain ? Previously we found out real ugly SMIME code that
hardcodes the use of SHA-1 :
http://groups.google.fr/group/mozilla.dev.tech.crypto/msg/7a15dafef963fe20
and here directly for the code
https://mxr.mozilla.org/comm-central/source/mailnews/extensions/smime/src/nsMsgComposeSecure.cpp#496
When I checked, I concluded that code reimplements everything on top on
low level pkcs#7 (nss/lib/pkcs7/) and makes no use of nss/lib/smime.
I need to check the code you digg out here. It seems very confusing.
--
dev-tech-crypto mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-crypto
