Enable passing cast channel certificate authority keys.

extensions/browser/api/cast_channel/cast_auth_util_openssl.cc

 // Copyright 2014 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "extensions/browser/api/cast_channel/cast_auth_util.h"
 
 #include "base/logging.h"
 
 namespace extensions {
 namespace core_api {
 namespace cast_channel {
 
 AuthResult AuthenticateChallengeReply(const CastMessage& challenge_reply,
                                       const std::string& peer_cert) {
   NOTREACHED();
   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