On 2010-06-12 00:50 PDT, Kaspar Brand wrote: > Sigh. I just came across this: > > http://support.microsoft.com/kb/2142236 > Non-Outlook email clients unable to decrypt email sent from Outlook 2010 > > which states under "Cause": > >> Outlook 2010 now more fully implements the Cryptographic Message >> Syntax (CMS) as documented in RFC3852. Outlook 2010 now uses >> subjectKeyIdentifier as the SignerIdentifier, whereas earlier >> versions used issuerAndSerialNumber. It seems that some clients may >> not yet support using subjectKeyIdentifier as the SignerIdentifier, >> as defined per the RFC. This results in it being unable to decrypt >> the message.
That's a quote directly from http://social.technet.microsoft.com/Forums/en-US/officeappcompat/thread/3a19bbc7-9c6b-40ec-823d-16fd88e8de38 or vice versa. > The statement about the SignerIdentifier is definitely incorrect. It > seems that Microsoft does not yet fully understand the issue - does > anyone here have straight contact to the Outlook dev team, or know > people who have? I'd be happy to help (i.e., explain the problem with > all the gory details), but would prefer to speak to someone who is also > able to fix the code, afterwards. I followed up on this with several posts in the forum page cited above. The moderator of that forum expressed interest in personally following up on the issue, but required that someone open a Microsoft support "case" which costs USD $99 (minimum) unless one subscribes to their support service. -- dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
