diff options
| author | Kenny Root <kroot@google.com> | 2016-10-31 09:40:11 -0700 |
|---|---|---|
| committer | Kenny Root <kroot@google.com> | 2016-11-04 19:29:40 +0000 |
| commit | a1d3063e3f0d9b8eb9b049bcaa0808f4ea6fba64 (patch) | |
| tree | 520380d7d1e6a05606c614811962130f38432487 /annotations/generate_annotated_java_files.py | |
| parent | 6facd9d7eb3b76137a5e32949bf29f91d3b9f4f9 (diff) | |
Make sure BouncyCastleProvider is initialized
When running these tests against an Android system when we're not built
as part of the system image (e.g., we have our own BouncyCastleProvider
instance), then we need to make sure our instance of
BouncyCastleProvider is initialized properly. The initialization happens
in its constructor.
In TestKeyStore the included version of BouncyCastleProvider does not
need to be inserted as a security provider since it's only used to
create X.509 certificates. However, BouncyCastle calls into itself for
some things like OID -> key type conversion. This relies on all of its
internal data structures being initialized properly. In particular there
is a keyInfoConverters field that must be populated to work correctly.
If keyInfoConverters is not populated, the generated certificate will
have a null PublicKey since it can't figure out what type of key it is.
Test: ran outside of CTS
Test: cts-tradefed run cts -m CtsLibcoreTestCases -a arm64-v8a
Bug: 31119038
Change-Id: I1bcc73a363cb9dac9e9decb9046d386d3394f1d9
Diffstat (limited to 'annotations/generate_annotated_java_files.py')
0 files changed, 0 insertions, 0 deletions