Certificate Authorities import dialog doesn't understand PKCS#7 file extension.

RESOLVED FIXED

Status

Camino Graveyard
Security
--
minor
RESOLVED FIXED
13 years ago
13 years ago

People

(Reporter: Tim Miller, Assigned: Simon Fraser)

Tracking

({fixed1.8})

Details

(Reporter)

Description

13 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2) Gecko/20050531 Camino/0.9+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2) Gecko/20050531 Camino/0.9+

Certs-only PKCS#7 files are used to transport multiple certificates (usually CAs) in one file.  These files often use the .p7b file extension.  Files with this extension are unselectable in the certificate import file chooser.  If the file extension is changed to, for example, .cer, the file and all certificates are properly imported.

Reproducible: Always

Steps to Reproduce:
1. Create a certs-only PKCS#7 named with .p7b
2. Attempt to import.  Can't select.
3. Rename file to .cer.
4. Import the certs.
In the Firefox version you can select any file, but the Camino filepicker locks you down to the explicitly listed filter extensions. Can the Camino filepicker be relaxed any? Or we could simply add .p7b to certManager.js 
http://lxr.mozilla.org/mozilla/source/security/manager/pki/resources/content/certManager.js#445
and also line 479 and 500.
Status: UNCONFIRMED → NEW
Ever confirmed: true

Comment 2

13 years ago
There seem to be many different file extensions in use for certificate files, recently we got a report about .pkcs7 file extension.

As we don't have a complete list of all extensions in use for certificate files, I recommend to relax the filepicker, too.
(Assignee)

Comment 3

13 years ago
This will need to be fixed in the Camino code.
Assignee: dveditz → sfraser_bugs
(Assignee)

Comment 4

13 years ago
Added ".p7b" and ".pkcs7" to the list of file extensions allowed when importing certificate files.

Fixed, trunk and branch.
Status: NEW → RESOLVED
Last Resolved: 13 years ago
Keywords: fixed1.8
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.