(This bug imported from BugSplat, Netscape's internal bugsystem. It was known there as bug #117217 http://scopus.netscape.com/bugsplat/show_bug.cgi?id=117217 Imported into Bugzilla on 03/14/00 11:22) With a "signers only" cert installed and attempting to send an encrypted message the following dialog appears. "This message cannot be encrypted or signed because you do not yet have an email certificate. Click on the security icon for more information about certificates" The dialog text needs to be corrected to inform the user that the certificate that is installed cannot be used to send encrypted messages. It is only valid for sending signed mail or something to that effect. I have this showing as an NT bug but my guess is that it is a problem on all platforms ------- Additional Comments From repka 05/13/98 11:32 ------- I think I can fix this bug pretty easily, but only if I'm allowed to add a new error message. In the past I've had some trouble getting such UI changes approved, due to the localization hit. So I'm waiting to hear from chofmann what the status of UI changes to 4.06 is. In the meantime, I'll mark this as intending to get fixed in 4.06, until I'm told otherwise. ------- Additional Comments From repka 06/15/98 17:38 ------- This isn't getting fixed in 4.06; bumping it up to 5.0. ------- Additional Comments From ksutton 07/17/98 11:56 ------- removed ksutton as QA Assigned new person YTBD ------- Additional Comments From paulmac 03/30/1999 11:40 ------- Moving all Security TFV 5.0 bugs to TFV 5.0 SF1in in preparation for moving them to Bugzilla (per leger) ------- Additional Comments From repka Jul-06-1999 16:11 ------- This is a usability problem that will affect dual-key environments. I don't know if someone wants to try to get it fixed under the auspices of the importance of dual-key. The problem is that the bug is in libmsg, in composec.c. It was introduced when jerdonek added the dual-key support there, reusing an existing error code that used to be applicable when only one mail certificate was supported. I think that the ultimate solution is to rework the interface used there, perhaps even to the point of have the compose code know nothing about certificates (it really doesn't have to, I think) but at least the error code(s) should be set on the security side not in the mail code. I don't know who should own this bug, but I'm going to let lord make a stab at that, since it may be important because it is a dual-key problem. If it isn't, then it's fine for it to get moved into some limbo-land for Cartman or NSS or even Messenger, and hopefully fixed in 5.0 when the interfaces between Cartman and Messenger are improved. (Or is that just wishful thinking?) ------- Additional Comments From marek Mar-01-2000 17:01 ------- mass-changing all old Communicator and Communicator Pro bugs filed for Comm. and Nav. versions older than 4.5 to WONTFIX. If you feel this was done in error, please reopen and reassign hong for consideration in 4.7x (assuming that you have a reproducible test case -- if you don't please don't reopen until you have one)

Giving new life to this bug, in bugzilla. Updating cc list to current list of people who might care. More changes to go in after the bug is officially reopened in this step.

Chris, as you might be able to figure out from the bug description text, this is not a problem in NSS. Perhaps not even a problem in PSM, though there should be a better interface between the client-side and PSM when asking to encrypt a message. (The client shouldn't have to know anything about signing vs. encryption certificates.) Something needs to get fixed, perhaps resulting in chases in all of the client, PSM and NSS. You seem like the best person to watch over that. It's also possible that with other dual-key work that the PSM folks did, this got taken care of. ddrinan might know, and in any case he belongs cc'd on this level of S/MIME problem.

Latering this one, since S/MIME isn't even yet a feature of Mozilla.

Adding myself as QA.

Verifying as later. Lowering priority and severity.

LATER is deprecated per bug 35839. Could someone who knows what's causing this direct it appropriately?

Marking fixed. The present message is "You need to setup one or more personal certificates before you can use this security feature. Would you like to learn how to do this now?

Verified.