Add a hook to inject trusted Cast roots for testing purposes.

extensions/common/cast/cast_cert_validator.h

 // 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.
 
 #ifndef EXTENSIONS_COMMON_CAST_CAST_CERT_VALIDATOR_H_
 #define EXTENSIONS_COMMON_CAST_CAST_CERT_VALIDATOR_H_
 
 #include <string>
 #include <vector>
 
@@ skipping 68 matching lines @@
                       CastDeviceCertPolicy* policy) WARN_UNUSED_RESULT;
 
 // Exposed only for unit-tests, not for use in production code.
 // Production code would get a context from VerifyDeviceCert().
 //
 // Constructs a VerificationContext that uses the provided public key.
 // The common name will be hardcoded to some test value.
 scoped_ptr<CertVerificationContext> CertVerificationContextImplForTest(
     const base::StringPiece& spki);
 
+// Exposed only for testing, not for use in production code.
+//
+// Injects trusted root certificates into the CastTrustStore.
+// Warning: Using this function concurrently with VerifyDeviceCert()
+//          is not thread safe.
+bool AddTrustAnchorForTest(const uint8_t* data,

[eroman, 2016/04/22 05:58:54]

Andrei suggested the name "AddDevTrustAnchorsForTest()" over email, what do you
think about that?

Assuming the dev trust anchors are fixed, this could internalize the certificate
data into the implementation rather than exposing a fully generic interface.

I am fine with either approach, so will defer to you/sheretov.

(My only concern with internalizing the data is ensuring the compilation is
smart enough to strip the unused data.)

[ryanchung, 2016/04/22 19:03:49]

We've decided to not bundle the test anchors for now. Also, Cast can ensure that
the test root is not compiled into production code.

+                           size_t length) WARN_UNUSED_RESULT;
 
 }  // namespace cast_crypto
 }  // namespace api
 }  // namespace extensions
 
 #endif  // EXTENSIONS_COMMON_CAST_CAST_CERT_VALIDATOR_H_