Debian Codegraph @

testing/pluto/nss-cert-11-ca-expired-responder-3conn-ikev2/description.txt

raw
1 old expired CA overlapping a new CA with random connection order
2
3 EAST has three template connections (old-ca, new-ca, and hog-ca).
4
5 On EAST each connection has its own root CA (same name), and that root
6 CA is used to generate a signed end certificate for WEST.
7
8 new-ca, new-west: the CA is valid (from 2 months ago), the cert from today
9 old-ca, old-west: the CA and end cert expired a month ago
10 hog-ca, hog-west: the CA and end cert expired a month ago
11
12 In the case of hog-ca, the connection also has groundhog enabled.
13
14 WEST has three corresponding connections (old-west, new-west,
15 hog-west).
16
17 WEST then tries to initiate each of these connections to EAST where
18 EAST:
19
20 - tries to authenticate the certificate chain using PKIX
21
22 The first pass through uses NOW. If there are any groundhogs, a
23 second pass will retry expired certificates using their expiration
24 date (flaging those certs as requiring a groundhog connection).
25
26 new-ca succeeds on the first pass using NOW for the time
27
28 old-ca and hog-ca succeed on the second pass by using their
29 expiration date
30
31 - searches for the best connection
32
33 If the cert is a groundhog, then non-groundhog connections are
34 skipped.
35
36 new-ca succeeds; no groundhog needed
37
38 old-ca is rejected as the only groundhog connection doesn't match
39 the CA
40
41 hog-ca succeeds because its connection is a groundhog and its CA
42 matches