Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
mozilla.dev.planning
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
Message from discussion NSS 3.12 codesize hit (Was: Milestone Scheduling)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Robert Sayre  
View profile  
 More options Jul 22 2007, 10:56 am
Newsgroups: mozilla.dev.planning
From: Robert Sayre <say...@gmail.com>
Date: Sun, 22 Jul 2007 10:56:20 -0400
Local: Sun, Jul 22 2007 10:56 am
Subject: Re: NSS 3.12 codesize hit (Was: Milestone Scheduling)
Print | View thread | Show original | Report this message | Find messages by this author

Mike Connor wrote:

>> That doesn't sound reasonable. We are going to accept a very large
>> body of code with known quality control problems.

> If you have evidence that libpkix has known quality control problems,

We do.  That is why it is so big. But, I agree it's likely that it
performs whatever PKI incantations it does correctly, in spite of that.

 > IMO, not taking

> 3.12 is the risky play, since we'll either need to find our own NSS
> hackers to maintain a fork of NSS 3.11, or take the hit anyway when we
> need security fixes that 3.12.x will get.  I'd much rather do that in
> alpha/beta than in security releases.

Well, I agree that we have to take it.

>>> That said, EV cert support is listed as a P1 (release blocker)
>>> requirement for Firefox 3, so we intend to ship it, and we'll take a
>>> ship delay to get it.  The decision was made, and nothing I've heard
>>> or seen has caused me to change my own perspective on that requirement.

>> We are going to support EV certs in Firefox 3. Thus far, they don't
>> have any measurable benefits, but it turns out we invented them, and
>> it would be too easy for our competitors to depict us as insecure if
>> we dropped them. So, here we are. We should at least assess the cost.

> If you're saying we should cut EV, say it, don't use codesize as an excuse.

I wasn't being facetious. I think EV is mystery meat, but we have to
ship it for the reasons I listed.

- Rob


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2012 Google