Closed Bug 272901 Opened 20 years ago Closed 20 years ago

Add root CA certificate NSS patch to Firefox 1.0 branch.

Categories

(Firefox :: General, enhancement)

1.0 Branch
enhancement
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 271585

People

(Reporter: hecker, Assigned: dveditz)

Details

(Whiteboard: [sg:fix])

Attachments

(2 files)

I've approved a bug of new CAs to have their root CA certificates added to
Mozilla, Firefox, Thunderbird, etc. Nelson Bolyard has created an NSS patch to
add those new CA certs to the NSS built-in cert library (see bug 271585). I'm
requesting that this NSS patch for the new CA certs be added to future versions
of Firefox. (Nelson can explain more about the actual patch and how it relates
to the official NSS releases.
Whiteboard: [sg:fix]
This is branch-only, since trunk is pulling NSS_CLIENT_TAG (see
http://lxr.mozilla.org/seamonkey/source/client.mk#183).  Branch pulls
AVIARY_1_0_20040515_BRANCH, though (see
http://lxr.mozilla.org/aviarybranch/source/client.mk#60).
Summary: Add root CA certificate NSS patch to Firefox → Add root CA certificate NSS patch to Firefox 1.0 branch.
Version: unspecified → 1.0 Branch
Hello.
I suppose it's thw right bug I am reporting my problem to.
My user-agent string for Firefox 1.0 is 
"Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107
Firefox/1.0" and I have problem with all certificates cause none of the signing
authorities is known.
Igor, your problem is unrelated to the issue in this bug report.
The problem you describe is a problem with your installation, not a
general problem with the product.  Please discuss it in 
news://news.mozilla.org:119/netscape.public.mozilla.crypto and not in
this bug report.  Thanks.
So FF 1.0.1 shipped last week, and did not contain the new certs that
were checked into NSS last December (NSS trunk and branch).  

I think *this* bug was created (in December) to try to ensure that 
FF 1.0.1 would include the roots.  So, why didn't it?
how about we set the necessary blocking-aviary flags to get some attention ;-)

reassigning to someone who might actually work on this.
Assignee: firefox → dveditz
Flags: blocking-aviary1.1?
Flags: blocking-aviary1.0.2?
> So, why didn't it?

Because no one managing the Aviary 1.0 branch took action on it.

Darin, this isn't an issue for 1.1 -- see comment 1.  But aviary branch branched
NSS, so....
Flags: blocking-aviary1.1?
Regardless of original intent, the branch changes appear to be handled in bug
271585 now.

*** This bug has been marked as a duplicate of 271585 ***
Status: NEW → RESOLVED
Closed: 20 years ago
Flags: blocking-aviary1.0.3?
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: