Enable passing cast channel certificate authority keys.

extensions/browser/api/cast_channel/cast_auth_util_openssl.cc

Index: extensions/browser/api/cast_channel/cast_auth_util_openssl.cc
diff --git a/extensions/browser/api/cast_channel/cast_auth_util_openssl.cc b/extensions/browser/api/cast_channel/cast_auth_util_openssl.cc
index 3ebceed1f107a848a36cfdeb2424c08e2592e85e..9bbd2e0bb21eba4ce71b7b439ff8c0db205c8ae9 100644
--- a/extensions/browser/api/cast_channel/cast_auth_util_openssl.cc
+++ b/extensions/browser/api/cast_channel/cast_auth_util_openssl.cc
@@ -16,6 +16,12 @@ AuthResult AuthenticateChallengeReply(const CastMessage& challenge_reply,
   return AuthResult();
 }
 
+bool SetTrustedCertificateAuthorities(const std::string& keys,
+                                      const std::string& signature) {
+  NOTREACHED();

[Ken Rockot(use gerrit already), 2014/10/27 17:17:50]

Why is this not reached? Clearly it's being linked, and I don't see any platform
restrictions on setAuthorityKeys.

[vadimgo, 2014/10/27 17:29:54]

Talking to Doug, only the nss version is used for build flavors that cast cares
about and openssl is only implemented to make other flavors link.
SetTrustedCertificateAuthorities implementation is consistent with
AuthenticateChallengeReply which are used to support the same functionality -
cast channel authentication.

+  return false;
+}
+
 }  // namespace cast_channel
 }  // namespace core_api
 }  // namespace extensions