Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(215)

Issue 1545034: Do not call NSS functions if NSS initialization failed.... (Closed)

Created:
10 years, 8 months ago by wtc
Modified:
9 years, 7 months ago
Reviewers:
agl
CC:
chromium-reviews, darin-cc_chromium.org, brettw-cc_chromium.org
Visibility:
Public.

Description

Do not call NSS functions if NSS initialization failed. R=agl BUG=36071 TEST=none Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=44728

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+12 lines, -3 lines) Patch
M base/nss_util.cc View 1 chunk +1 line, -0 lines 0 comments Download
M net/base/x509_certificate_nss.cc View 2 chunks +4 lines, -0 lines 0 comments Download
M net/socket/ssl_client_socket_nss.cc View 2 chunks +7 lines, -3 lines 0 comments Download

Messages

Total messages: 3 (0 generated)
wtc
10 years, 8 months ago (2010-04-14 02:05:12 UTC) #1
agl
LGTM. I would also be fine with just bailing out if NSS init fails.
10 years, 8 months ago (2010-04-14 14:10:10 UTC) #2
wtc
10 years, 8 months ago (2010-04-14 16:51:28 UTC) #3
On 2010/04/14 14:10:10, agl wrote:
> 
> I would also be fine with just bailing out if NSS init fails.

I agree.  It's impractical to check before all NSS calls.  I
only protect the SSL and certificate code in this CL, but the
crypto code in base also calls NSS.

It's just that I don't know how to display UI to tell the user why
we're bailing out.

Powered by Google App Engine
This is Rietveld 408576698