summaryrefslogtreecommitdiffstats
path: root/security/manager/ssl/tests/unit/test_onecrl/sample_revocations.txt
blob: e8d9db7465352b5a0f3edceb777de58d75b1bb3a (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
# a sample revocations.txt for tests
# Lines starting with '#' are ignored - as are empty lines like this:

# otherwise:
# non-empty lines are treated as base-64 encoded DER DN data (e.g. issuer or
# subject)
# ...unless the line starts with a ' ' (space) character, in which case it's
# assumed to be base-64 encoded DER serial data, or
# the line starts with a '\t' (tab) character, in which case it's assumed to
# be a base-64 encoded SHA256 hash of a public key

# First a serial with no issuer to ensure this doesn't cause parsing to fail
# (there should be an issuer first, but we need to test this won't fail)
 dGVzdA==
# next, let's ensure data that isn't valid base64 doesn't cause breakage.
 this serial isn't valid base64 (but then there's no issuer anyway)
Neither is this issuer, though the serial is fine
 dGVzdA==
dGVzdA==
 in this case, issuer is fine but not the serial
# Next two entries; we can add valid base-64 encoded data for some basic tests:
# issuer is "some imaginary issuer" base-64 encoded
# and serial "serial." base-64 encoded
c29tZSBpbWFnaW5hcnkgaXNzdWVy
 c2VyaWFsLg==
# issuer is "another imaginary issuer" base-64 encoded
# serials are "serial." and "serial2." base-64 encoded
YW5vdGhlciBpbWFnaW5hcnkgaXNzdWVy
 c2VyaWFsLg==
 c2VyaWFsMi4=
# subject is "some imaginary subject", base-64 encoded
# pubKeyHash is the sha256 hash of "some imaginary pubkey" base-64 encoded
c29tZSBpbWFnaW5hcnkgc3ViamVjdA==
	blBNgTxORaii2Sqe9bQcYsmfJ3kiXOLiKLzQNJ2wZYE=
# and some more data to ensure that mixed items don't cause parsing failure
a DN
 a serial
	a hash
 another serial