Closed
Bug 99540
Opened 24 years ago
Closed 24 years ago
OK button in EDIT CA CERTIFICATE TRUST SETTINGS dialog does not work.
Categories
(Core Graveyard :: Security: UI, defect, P2)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
psm2.2
People
(Reporter: lgopal, Assigned: ssaux)
Details
Build : 20010913
1. Create a new profile.
2. Connect to any https site. Import the website cert.
3. using
EDIT->PREFERENCES->PRIVACY&SECURITY->CERTIFICATE->MANAGECERTIFICATE->WEBSITE
select the website cert. Select the cert. Click on Edit. From EDIT WEB SITE
CERTIFICATE SETTINGS click EDIT CA TRUST. Check mark - > This certificate can
identify web sites. Click on OK button. Nothing happens .
| Reporter | ||
Updated•24 years ago
|
Priority: -- → P2
| Reporter | ||
Comment 1•24 years ago
|
||
While accquring a SSL cert the CA does not get imported into the browser.
The Button EDIT CA TRUST should be dislabled when the CA is not trusted by the
browser.
Changing Priority form P2 to P1 as it confuses the user.
Priority: P2 → P1
| Assignee | ||
Comment 2•24 years ago
|
||
lakshmi.
When the CA is not trusted but is present in the cert db, the edit button makes
sense (this way you can trust it)
There may be a problem if the CA cert is not in the cert db and we still present
a edit CA button.
Need a better test case.
Target Milestone: --- → 2.2
| Reporter | ||
Comment 3•24 years ago
|
||
Teh test case is correct. Why do you allow to edit a CA trust when the CA is not
present.
All that it needs to be done is when the CA is not present disable the
"EDIT CA TRUST button".
Updated•24 years ago
|
QA Contact: bsharma → junruh
| Assignee | ||
Comment 5•24 years ago
|
||
The instructions on how to reproduce this bug are at best incomplete:
In order to import a web site certificate, one must visit a site with a
certificate that the browser complains about, such as when the Issuer is not
recognized.
Using the 6.2 release, I visited
https://beaver.mcom.com/moztesting, whose server cert is signed by a CA one is
unlikely to have in one's browser.
I'm prompted by the unknown CA dialog, and I select to trust the cert by
checking the check box (i.e., I "import" the server cert in my database).
I subsequently followed Lakshmi's instructions by going to the cert
manager->web-sites, selecting the beaver.mcom.com cert, clicking on Edit, then
on Edit CA trust. The result is that I got a dialog stating that the CA cert was
not found.
This is an acceptable behavior.
If the bug is that the Edit CA Trust does nothing, then that's a worksforme. If
the bug is that there shouldn't be either a dialog stating that CA cert was not
found nor an Edit CA trust button, that's a wontfix. I prefer that the browser
warns the person.
qawanted, worksforme.
Status: NEW → RESOLVED
Closed: 24 years ago
Keywords: qawanted
Priority: P1 → P2
Resolution: --- → WORKSFORME
Comment 6•24 years ago
|
||
Verified worksforme. I agree with ssaux. This is the same behavior as 4.7X with
PSM.
Status: RESOLVED → VERIFIED
VERIFIED WORKSFORME almost 8 years ago. Removing QAWANTED.
Keywords: qawanted
Updated•9 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•