Extract key metadata from the client certificate on Windows.

Extract key metadata from the client certificate on Windows.

Querying CAPI and CNG seem to both fail on some environments. Rather
than hope smartcards and whatnot implement the necessary features,
bypass Windows APIs entirely and extract the information out of the
public key in the certificate using BoringSSL APIs.

BUG=468345
Committed: https://crrev.com/c60e333c3f3f8e00fb14aff60434de2b79a28157
Cr-Commit-Position: refs/heads/master@{#321287}

[davidben, 2015-03-18 21:42:32]

davidben@chromium.org changed reviewers:
+ rsleevi@chromium.org

[davidben, 2015-03-18 21:42:32]

https://codereview.chromium.org/1002013009/diff/20001/net/ssl/openssl_platfor...
File net/ssl/openssl_platform_key_win.cc (left):

https://codereview.chromium.org/1002013009/diff/20001/net/ssl/openssl_platfor...
net/ssl/openssl_platform_key_win.cc:452: if (degree == 0) {
I'm not sure why I called it degree here. That was just wrong to begin with; the
values are taken modulo the order. (Though either way the sizes end up being the
same in practice.)

https://codereview.chromium.org/1002013009/diff/20001/net/ssl/openssl_platfor...
File net/ssl/openssl_platform_key_win.cc (right):

https://codereview.chromium.org/1002013009/diff/20001/net/ssl/openssl_platfor...
net/ssl/openssl_platform_key_win.cc:41: #include
"net/ssl/scoped_openssl_types.h"
This will likely cause a minor merge conflict, but it's easily resolvable.

[Ryan Sleevi, 2015-03-19 03:20:05]

lgtm

[davidben, 2015-03-19 04:01:41]

The CQ bit was checked by davidben@chromium.org

[commit-bot: I haz the power, 2015-03-19 04:01:54]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1002013009/40001

[commit-bot: I haz the power, 2015-03-19 04:05:24]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2015-03-19 04:05:51]

Patchset 3 (id:??) landed as
https://crrev.com/c60e333c3f3f8e00fb14aff60434de2b79a28157
Cr-Commit-Position: refs/heads/master@{#321287}