diff options
| author | davidben@chromium.org <davidben@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-08-17 20:00:43 +0000 |
|---|---|---|
| committer | davidben@chromium.org <davidben@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-08-17 20:00:43 +0000 |
| commit | 701e869b30deffda579c5c413cf1d73defee34fa (patch) | |
| tree | 82ac5b9f26131080c7a6f90404393393bcea0114 /printing/printing_context_win.cc | |
| parent | 95fd5facaff32caa53dd58dc9139e07140d8834c (diff) | |
| download | chromium_src-701e869b30deffda579c5c413cf1d73defee34fa.zip chromium_src-701e869b30deffda579c5c413cf1d73defee34fa.tar.gz chromium_src-701e869b30deffda579c5c413cf1d73defee34fa.tar.bz2 | |
Clean up the client certificate filtering code on Linux
Instead of filtering over all certificates and then picking the ones suitable
for client auth, NSS provides a function that does this in one go. In addition,
delay checking for the private key until we actually send the certificate.
While this means we may potentially offer a client certificate with no matching
private key, such a store should not exist. This avoids requiring us
authenticate to every certificate offered. In addition, it delays the password
dialog, when we implement it, until after the user has designated that they are
interested in a certificate.
This mirrors Firefox's use of NSS.
R=wtc
BUG=none
TEST=linux ssl client auth works
Review URL: http://codereview.chromium.org/3177018
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@56404 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'printing/printing_context_win.cc')
0 files changed, 0 insertions, 0 deletions