diff options
| author | lloyd <[email protected]> | 2006-08-23 10:01:22 +0000 |
|---|---|---|
| committer | lloyd <[email protected]> | 2006-08-23 10:01:22 +0000 |
| commit | b8844f2bfca984285f9cfe61bed56cf5d9c33705 (patch) | |
| tree | bab88d26c8deca5fef64024776866bc0312060ba /misc/python | |
| parent | 0315cd9112b467b9a50f2ac959c74144622390d6 (diff) | |
Add some comments to the NIST test suite results file with regards to
results that have been changed from the official expected results.
Diffstat (limited to 'misc/python')
| -rw-r--r-- | misc/python/results.txt | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/misc/python/results.txt b/misc/python/results.txt index a8e2f30ba..7a3824001 100644 --- a/misc/python/results.txt +++ b/misc/python/results.txt @@ -1,3 +1,4 @@ +# This is the file of expected results for nisttest.py test01 verified test02 signature_error test03 signature_error @@ -16,6 +17,8 @@ test15 verified test16 verified test17 verified test18 verified +# changed; should be no_revocation_data_available, but I don't want to +# force people to use CRLs test19 verified test20 cert_is_revoked test21 cert_is_revoked @@ -42,8 +45,11 @@ test61 cert_chain_too_long test62 verified test63 verified test64 signature_error +# changed; I have no idea why this test is supposed to fail test65 verified test66 crl_issuer_not_found +# changed; one of the CRLs has an unknown creator, so we fail +# prior to getting to the end-entity check test67 crl_issuer_not_found test68 cert_is_revoked test69 cert_is_revoked |