The ability to generate self-signed certificates is important in order to get a secure infrastructure deployed. However, this means that when you receive a message from a correspondent, and you already have a different certificate saved, then you have to prompt the user to ask which (or maybe both) certificates to keep.
In the 'spec 2', I prefer option 3 as it doesn't consume scren real estate with priority/security settings. I have my preferences set to always encrypt (in 4.7x) and end up clikcing the 'ok' when a recipient doesn't have a cert. The only enhancement that I might want would be to be able to mark certain recipients as 'plain text only', and this would disable the signing as well. [THis arises from mailing lists where the list members get upset by having s/mime signatures sent to the list (and digest). You can argue that this is the fault of the mailing list software (or the users on the list....).] This case is the only time in the current 4.7x that I use the options tab when sending a message. Philip Jennifer Glick wrote: > Draft spec now posted here: > http://www.mozilla.org/mailnews/specs/security/ > > Please post comments to the mail-news and crypto newsgroups.
