Mail/News Performance Effort Underway
Friday November 2nd, 2001
Seth Spitzer today sent an update out about what the Mail/News team is doing to meet their goals for Mozilla 1.0. They'll be focusing almost 100% of their effort for at least the next two milestones (0.9.7, 0.9.8) on Footprint and Performance of the various parts of Mail, News, and Addressbook. Not only will they be focusing on it, they'll also be locking down their part of the tree and only accepting performance or footprint fixes. Very few exceptions will be made. Click the Full Article link to see Seth's full post.
#5 Re: PGP is not even considered
Friday November 2nd, 2001 10:36 PM
You are replying to this message
The arch document I found in that bug are some rough notes about adding some header and handling the encryption/signing with "converters".
I haven't checked the implementation which is being cheked in. But reading through this "Mail: Encryption and Signing" document (which is hosted at "<http://www.mozilla.org/mailnews/specs/security/>", could it be more official/canonical? ).
This document is clearly S/MIME only, I quote:
"If the client has found a certificate for all the current addressees, the 'Send' button is modified to incorporate a "will be encrypted" icon (closed lock)."
What if those certificates (keys?) are from different encryption schemes? The issue is not mentioned in "Issues", nor it's mentioned as one of the cases whoen with screenshots. The spec is very detailed about visual UI feedback, but it doesn't specify how it will show to which scheme the keys for a recipient belong.
But there's no need to look for this details. The summary of this document's content clearly says it all:
The S/MIME features of Mail enhance the security of your emails. Specifically, these features:
* Ensure the privacy of your email while it travels from your machine to your recipient's machine using high-grade encryption. * Enable you to identify yourself and others in email messages by way of digital signatures. * Ensure that no one can modify the email while it travels from your machine to your recipient's machine."