Update the NSS patches. Add snapstart2.patch and peercertchain.patch....

Update the NSS patches.  Add snapstart2.patch and peercertchain.patch.
Tweak sslimpl.h to eliminate one conflict when applying clientauth.patch.
Unfortunately one conflict in sslimpl.h and one conflict in ssl3con.c still
remain in clientauth.patch.

Add the applypatches.sh script to make it easier to apply the patches.

R=agl
BUG=none
TEST=none

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=75311

[wtc, 2011-02-17 00:04:29]

agl: please review this patch.  I'm getting ready to merge with NSS 3.12.9.

I will try to upstream as many NSS patches as possible.

rsleevi: just FYI.

http://codereview.chromium.org/6538005/diff/2001/net/third_party/nss/ssl/ssli...
File net/third_party/nss/ssl/sslimpl.h (left):

http://codereview.chromium.org/6538005/diff/2001/net/third_party/nss/ssl/ssli...
net/third_party/nss/ssl/sslimpl.h:834: PRBool                nextProtoNego;/*
Our peer has sent this extension */
Note that this line comes from nextproto.patch, which causes a conflict with
clientauth.patch that I generated with CVS.

Someone with git prowess can solve this problem better.  I just moved the
NSS_PLATFORM_CLIENT_AUTH code elsewhere.

[Ryan Sleevi, 2011-02-17 00:39:31]

wtc: Am I correct in assuming by "as many as possible" you mean excluding the
platform auth patch? If you had been planning on including it, I'd suggest
holding off, though I'd be surprised if it would even be upstreamed, as I'm
having to rework some of it for the NCrypt/CNG case. NCrypt keys cannot be
duplicated, so ownership cannot be both cached in the Chromium code and have
ownership transferred/shared with the NSS side.

[wtc, 2011-02-17 00:43:06]

rsleevi: clientauth.patch cannot be upstreamed in the current form.  Don't
worry.

[agl, 2011-02-17 16:24:27]

LGTM