S/MIME Capabilities not included by Mail.app
Problem ID: 6650735
05-Mar-2009 12:15 PM
Summary:
In order to properly integrate with other mail clients (notably Outlook, Outlook Express, Windows Live Mail) it is beneficial to include S/MIME Capabilities information in signed S/MIME messages detailing which encryption algorithms are acceptable. Both Windows mail clients and Thunderbird 2 & 3 include this information.
Other systems and email clients rely on this information to determine which crypto algorithms to use.
When an Apple Mail user signs a message to a Windows user, Windows properly looks for the sMIMECapabilities signed attribute that RFC3851 says SHOULD be included. When it doesn't find anything it marks the client as S/MIME V2-only and, thus, will only use 40-bit encryption.
*Any chance of getting Mail.app to implement this SHOULD from RFC3851?*
Been waiting a year and have seen a major version upgrade and...nothing.
05-Mar-2009 12:15 PM
Summary:
In order to properly integrate with other mail clients (notably Outlook, Outlook Express, Windows Live Mail) it is beneficial to include S/MIME Capabilities information in signed S/MIME messages detailing which encryption algorithms are acceptable. Both Windows mail clients and Thunderbird 2 & 3 include this information.
Other systems and email clients rely on this information to determine which crypto algorithms to use.
When an Apple Mail user signs a message to a Windows user, Windows properly looks for the sMIMECapabilities signed attribute that RFC3851 says SHOULD be included. When it doesn't find anything it marks the client as S/MIME V2-only and, thus, will only use 40-bit encryption.
*Any chance of getting Mail.app to implement this SHOULD from RFC3851?*
Been waiting a year and have seen a major version upgrade and...nothing.
20" Intel iMac x 4, 17" G4 iMac upg to 1GB 160GB, 2.2GHz MacBook, Mac OS X (10.6.2)
