Expose OpenSSL's key_exchange_info in the content API

net/ssl/ssl_info.h

Index: net/ssl/ssl_info.h
diff --git a/net/ssl/ssl_info.h b/net/ssl/ssl_info.h
index da20817c2e688908c4f83e1541ecd5f3d44ba906..7627e9508eaf1b8011c7980c641077ddd64213af 100644
--- a/net/ssl/ssl_info.h
+++ b/net/ssl/ssl_info.h
@@ -60,6 +60,12 @@ class NET_EXPORT SSLInfo {
   // -1 means the security strength is unknown.
   int security_bits;
 
+  // Security information of the SSL connection handshake.
+  // The meaning depends on the cipher used, see |SSL_SESSION|'s
+  // key_exchange_info for more information.
+  // A zero indicates that the value is unknown.

[mmenke, 2015/08/26 15:28:37]

Is there a case where for some cipher, an actual value of 0 is possible?

[sigbjorn, 2015/08/26 15:46:15]

No. It will hold either a bit strength (which necessarily is greater than 0), or
an enum value.

In theory OpenSSl's internal representation might grow to hold an enum value of
0 in the future, see https://boringssl-review.googlesource.com/#/c/5280/, search
for "One question for Adam though". It could still avoid reporting it as 0 to
the content layer, even if that was the case.

+  int key_exchange_info;
+
   // Information about the SSL connection itself. See
   // ssl_connection_status_flags.h for values. The protocol version,
   // ciphersuite, and compression in use are encoded within.