Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(990)

Side by Side Diff: net/data/verify_certificate_chain_unittest/README

Issue 2797303006: Save the private keys used by generated verify_certificate_chain tests. (Closed)
Patch Set: fix for case-insensitive filesystems Created 3 years, 8 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
OLDNEW
1 This directory contains test data for verifying certificate chains. 1 This directory contains test data for verifying certificate chains.
2 2
3 It contains the following types of files: 3 It contains the following types of files:
4 4
5 =============================== 5 ===============================
6 generate-*.py 6 generate-*.py
7 =============================== 7 ===============================
8 8
9 Generates the file for an individual test case. If the python file was 9 Generates the file for an individual test case. If the python file was
10 named generate-XXX.py, then the corresponding output will be named 10 named generate-XXX.py, then the corresponding output will be named
11 XXX.pem. 11 XXX.pem.
12 12
13 =============================== 13 ===============================
14 generate-all.sh 14 generate-all.sh
15 =============================== 15 ===============================
16 16
17 Runs all of the generate-*.py scripts and does some cleanup. 17 Runs all of the generate-*.py scripts and does some cleanup.
18 18
19 =============================== 19 ===============================
20 keys/XXX/*.key
21 ===============================
22
23 The keys used/generated by test XXX. The privat keys shouldn't be needed to run
mattm 2017/04/10 23:13:00 private
eroman 2017/04/10 23:56:30 Done.
24 the tests, however are useful when re-generating the test data to have stable
25 results (at least for signature types which are deterministic, like RSASSA
26 PKCS#1 which is used by most of the certificates data)
27
28 ===============================
20 *.pem 29 *.pem
21 =============================== 30 ===============================
22 31
23 Each .pem file describes the inputs for certificate chain verification, and the 32 Each .pem file describes the inputs for certificate chain verification, and the
24 expected result. These are the PEM blocks that each file contains and their 33 expected result. These are the PEM blocks that each file contains and their
25 interpretation: 34 interpretation:
26 35
27 CERTIFICATE: 36 CERTIFICATE:
28 37
29 These PEM blocks describe the ordered chain of certificates starting from the 38 These PEM blocks describe the ordered chain of certificates starting from the
(...skipping 31 matching lines...) Expand 10 before | Expand all | Expand 10 after
61 70
62 This PEM block describes the expected result from verifying the path. 71 This PEM block describes the expected result from verifying the path.
63 72
64 - There must be exactly one such PEM block 73 - There must be exactly one such PEM block
65 - Its contents are a string with value of either "SUCCESS" or "FAIL" 74 - Its contents are a string with value of either "SUCCESS" or "FAIL"
66 75
67 ERRORS: 76 ERRORS:
68 77
69 This PEM block is a pretty-printed textual dump of all the errors, as given by 78 This PEM block is a pretty-printed textual dump of all the errors, as given by
70 CertErrors::ToDebugString(). 79 CertErrors::ToDebugString().
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698