Age | Commit message (Collapse) | Author |
|
To avoid flaky tests (e.g., device date is not correct), we should set a
date on the PKIX path verification parameters.
Bug: 26716600
Change-Id: Ie7c18c9cff63b2c8ea4bb050593d79db39401dd8
|
|
The test description lists the CRL signing key and the CA signing key in
the description's expected path, but it should only be the CA signing key
in the path.
This change fixes all the tests that had this ambiguity.
Bug: 8030138
Change-Id: I4edd999d94a05d80a0a2e03e49d9a4025bd9bbfe
|
|
Some tests were listed with multiple apparent intermediates in the
documentation, but they were actually one CA to sign the cert and one CA
to sign the CRL. This change allows the fixing of the tests to be able
to assert separate path from general cert collections.
Bug: 8030138
Change-Id: I6dab5be846650c26ed0ed9eb9d8194d93fc85908
|
|
In an effort to stay close to what the NIST PKITS documentation
specifies for these tests, be explicit about our PKIX parameters we are
expecting.
Change-Id: Ifd02328fda701016f0ad947e8020ae2dec4737ad
|
|
Change-Id: I44b8e759e38f074174df745c39979acc5334c778
|