On Apr 10, 7:37 am, Jean-Marc Desperrier <jmd...@free.fr> wrote: > On 31/03/201017:11, Kaspar Brand wrote: > > > On 31.03.201007: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/... > > > 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/7a15dafef96... > and here directly for the > codehttps://mxr.mozilla.org/comm-central/source/mailnews/extensions/smime... > > 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.
According to the link at http://social.technet.microsoft.com/Forums/en-US/officeappcompat/thread/3a19bbc7-9c6b-40ec-823d-16fd88e8de38 Outlook 2010 is OL2010 is using “sender key ID” instead of “issuer name and serial number” – as per an SMIME standard, but can be reverted to an older style using a registry key. I suspect that NSS is not supporting "sender key ID" yet/properly. I think Thunderbird needs this fixed... -- dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
