| f28e4178ccc8943f0439f63eaf69e11dc798831f |
|
04-May-2017 |
Adam Vartanian <flooey@google.com> |
Add SSLEngine and SSLSocket cipher suite docs to autodocs.
Bug: 35793879
Bug: 31526422
Test: Executed, replaced tables in Javadoc
(cherry picked from commit 22051136d1344e34c05659420bc49372040bd75e)
Change-Id: Ic114094dfa1c3ea6f55b65e468adda49e3153302
|
| 22051136d1344e34c05659420bc49372040bd75e |
|
04-May-2017 |
Adam Vartanian <flooey@google.com> |
Add SSLEngine and SSLSocket cipher suite docs to autodocs.
Bug: 35793879
Test: Executed, replaced tables in Javadoc
Change-Id: I9c0c857f2facc4b724b8c95b773c73f4060e18bd
|
| 6d9dab5697fd9696b03c2cfc1e73a52201870c16 |
|
15-Mar-2017 |
Adam Vartanian <flooey@google.com> |
Add Cipher support to autodocs.
Ciphers are more complicated than other categories because providers can
declare that they provide a base algorithm but users request an
algorithm/mode/padding triple, so we need to investigate the possible
values of that triple and see which ones actually end up available.
We ignore all the PBE ciphers because they're a mess and we don't
want them to show up in the documentation.
The starting API level for AES/GCM/NOPADDING is actually an educated
guess, it's approximately correct but might be off by one or two.
I'll update it if I later get better information.
Bug: 35793879
Test: Ran run_update_crypto_support.sh
Change-Id: Ifb827818626690ff223f691c8297731790074283
|
| 652e5d1f4a7d2af60836a7930ae6c2081239c80e |
|
14-Mar-2017 |
Adam Vartanian <flooey@google.com> |
Add autodoc support for Signature.
There are a few algorithms that used to be known by one name but now are
known by another, but the first name still shows up in our documentation,
so I added handling to continue to support those names.
I also had to do a little bit of sleuthing on when certain algorithms
appeared, because they certainly were before API 26 but our API 25 docs
don't mention them. They may be slightly off in one direction or another.
Bug: 35793879
Test: Ran run_update_crypto_support.sh
Change-Id: Ifc3e6fa3177afd82012d75eaaf7ecb26d750659d
|
| 9ae0b401654f2faf408bb37808e7f6a5ede976b6 |
|
08-Mar-2017 |
Adam Vartanian <flooey@google.com> |
Add tools for generation of crypto algorithm support documentation.
The tool suite consists of:
* crypto_support.json, a JSON file that stores the name and API levels
of all the algorithms we provide or have provided in the past.
* ListProviders.java, which runs on a device and outputs a list of
all the algorithms provided by the security providers.
* update_crypto_support.py, which consumes the output of ListProviders
and rewrites the JSON file to reflect the currently-supported
algorithms.
* run_update_crypto_support.sh, which ties the previous two together
to make it more convenient to run.
* format_supported_algorithm_table.py, which reads the JSON file and
generates a set of HTML tables that can be copied-and-pasted into
documentation.
The intermediate JSON file makes it a lot easier to verify that the
tools have done the right thing after an update, instead of having
to compare the HTML output.
Only Mac and MessageDigest are included for now. I'll add additional
categories of algorithms in a future change, but I wanted to send the
code out for review before spending the time to add the data on
formerly-provided algorithms that's in the class documentation.
Bug: 35793879
Test: libcore/tools/update_crypto_support_test.py
Change-Id: Ib14722b2703cbbc45438d1168395e4e1194515a2
|