Closed Bug 263912 Opened 20 years ago Closed 19 years ago

If I try loading a .p12 certificate, the browser does a no-op

Categories

(Core Graveyard :: Security: UI, defect)

Other Branch
x86
Linux
defect
Not set
major

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: kernel, Assigned: KaiE)

References

()

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040803
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040803

If I try loading a p12-encoded client-side certificate into the browser, nothing
happens.  The previous page is not cleared, no error is produced, nothing.

Reproducible: Always
Steps to Reproduce:
1.Try loading the given .p12 file
2.
3.

Actual Results:  
Nothing happens, except the location bar is now the .p12 url.

Expected Results:  
Mozilla should open a dialog box asking if I want to import this certificate,
and would I please enter the password that the certificate is encrypted with. 
At least that's what IE and Opera do.

The certificate is signed by a CA that I created and self-signed, reachable at
https://jtmmx.jacobs.ca:442/cacert.pem
For an un-encrypted session, try:
http://jtmmx.jacobs.ca:89/newcert.p12

If you do succeed in getting a dialog box happening, the password on the
certificate is asdfasdf.

This is on a Fedora Core 2 box.
-> psm
Assignee: dveditz → kaie
Component: Security: CAPS → Client Library
Product: Browser → PSM
Version: Trunk → unspecified
Product: PSM → Core
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/
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
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.