Closed
Bug 226104
Opened 21 years ago
Closed 19 years ago
Examined certificate cannot be Accepted beyond temporary
Categories
(MailNews Core :: Security: S/MIME, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: jim, Assigned: KaiE)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031117 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031117 Sometimes when I send an email a dialog box for examining an Unknown Authority for a Certificate comes up. I look at it, I am aware that it is correct, and I want to accept it as the cert from here on out. (This bug is not an issue in TB, BTW.) The "Temporarily Accept" choice will work, but the permanent one just has the dialog come right back up. I will post Screenshot soon and the info for the cert. I can reproduce on a regular basis, but I think there is a necessary time delay for the temporary setting to last. Once it is no longer active as a temporary "OK", I get the error. Reproducible: Sometimes Steps to Reproduce: 1 2. 3. Actual Results: Dialog comes rigth back up for me to accept cert Expected Results: If I say I allow it permanently, it should allow it permanently.
Comment 1•21 years ago
|
||
no security bug, looks more like a problem with crypto
Assignee: sspitzer → ssaux
Component: Security: General → Client Library
Product: MailNews → PSM
QA Contact: junruh → bmartin
Version: Trunk → unspecified
Updated•21 years ago
|
Assignee: ssaux → kaie
Assignee | ||
Comment 2•21 years ago
|
||
Did it work correctly with older versions of Mozilla. In other words, is this bug a regression?
Updated•20 years ago
|
Component: Client Library → S/MIME
Comment 3•19 years ago
|
||
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 4•19 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•