strongswan_pki---estca(1)

1PKI --ESTCA(1)                    strongSwan                    PKI --ESTCA(1)
2
3
4

NAME

6       pki --estca - Get CA certificate[s] from an EST server
7

SYNOPSIS

9       pki --estca --url url --cacert file [--caout file] [--outform encoding]
10                   [--force] [--debug level]
11
12       pki --estca --options file
13
14       pki --estca -h | --help
15

DESCRIPTION

17       This sub-command of pki(1) gets CA certificates via https from  an  EST
18       server  using  the  /cacerts  operation  of  the Enrollment over Secure
19       Transport protocol (RFC 7030).
20

OPTIONS

22       -h, --help
23              Print usage information with a summary of the available options.
24
25       -v, --debug level
26              Set debug level, default: 1.
27
28       -+, --options file
29              Read command line options from file.
30
31       -u, --url url
32              URL of the SCEP server.
33
34       -C, --cacert file
35              CA certificate in the trust chain used for EST TLS server signa‐
36              ture verification.  Can be used multiple times.
37
38       -c, --caout file
39              If  present,  path where the fetched root CA certificate file is
40              stored to.  If several CA certificates are downloaded, then  the
41              value  of  --caout  is used as a template to derive unique file‐
42              names (*-1, *-2, etc.) for the intermediate or sub  CA  certifi‐
43              cates.  If a file suffix is missing, then depending on the value
44              of --outform either .der (the default) or .pem is  automatically
45              appended.  If the --caout option is missing and --outform is set
46              to pem then a PEM-encoded CA certificate bundle  is  written  to
47              stdout.
48
49       -f, --outform encoding
50              Encoding of the created certificate file. Either der (ASN.1 DER)
51              or pem (Base64 PEM), defaults to der.
52
53       -F, --force
54              Force overwrite of existing files.
55

EXAMPLES

57       To save some typing work the following command line options are  stored
58       in a est.opt file:
59
60       --url https://pki.strongswan.org:8443
61       --cacert tlsca.crt
62       --cacert tlsca-1.crt
63
64       NOTE: For a successful HTTPS connection, trust must be established into
65       the EST server certificate. The TLS trust chain including the  root  CA
66       certificate  and  optionally intermediate CA certificates must be given
67       using [multiple] --cacert options.
68
69       An EST server sends a root CA and an intermediate CA certificate:
70
71       pki --estca --options est.opt --caout myca.crt
72
73       negotiated TLS 1.3 using suite TLS_AES_256_GCM_SHA384
74       received TLS server certificate 'C=CH, O=strongSwan Project, CN=pki.strongswan.org'
75         using certificate "C=CH, O=strongSwan Project, CN=pki.strongswan.org"
76         using trusted intermediate ca certificate "C=CH, O=strongSwan Project, CN=strongSwan Issuing CA"
77         using trusted ca certificate "C=CH, O=strongSwan Project, CN=strongSwan Root CA"
78         reached self-signed root ca with a path length of 1
79       Root CA cert "C=CH, O=strongSwan Project, CN=strongSwan Root CA"
80         serial: 65:31:00:ca:79:da:16:6b:aa:ac:89:e2:a8:f9:49:c3:10:ab:64:54
81         SHA256: 96:70:50:51:cd:b9:e7:94:6b:04:f6:15:45:80:fc:90:85:01:71:2a:f6:4f:d1:1b:2d:a1:7e:eb:bf:dd:be:86
82         SHA1  : 8e:f3:78:b0:34:a6:c1:6a:7b:c6:f5:91:eb:e5:46:9b:0d:0a:a7:ba (jvN4sDSmwWp7xvWR6+VGmw0Kp7o)
83       Root CA equals trusted TLS Root CA
84       Root CA cert is trusted, valid until Aug 12 15:51:34 2032, 'myca.crt'
85       Sub CA cert "C=CH, O=strongSwan Project, CN=strongSwan Issuing CA"
86         serial: 74:f9:7e:72:7d:b8:fd:f2:c6:e5:1b:fa:37:f9:cb:87:bf:9c:ea:e2
87         SHA256: a3:5b:4b:12:d5:8f:68:7b:05:11:08:27:f5:42:62:b8:b5:01:1b:19:37:9c:28:78:5d:37:08:69:6a:8c:07:bf
88         SHA1  : 8c:e6:67:67:c2:23:89:7b:d0:bc:b1:50:d2:1c:bc:8d:8d:69:15:11 (jOZnZ8IjiXvQvLFQ0hy8jY1pFRE)
89         using certificate "C=CH, O=strongSwan Project, CN=strongSwan Issuing CA"
90         using trusted ca certificate "C=CH, O=strongSwan Project, CN=strongSwan Root CA"
91         reached self-signed root ca with a path length of 0
92       Sub CA cert is trusted, valid until Aug 12 15:51:34 2027, 'myca-1.crt'
93
94       NOTE: The trusthworthiness of the root CA certificate is  either  veri‐
95       fied automatically if the Root CA certificate of the TLS trust chain is
96       the same as that of the Issuing CA. Otherwise trust has  to  be  estab‐
97       lished manually by verifying the SHA256 or SHA1 fingerprint of the DER-
98       encoded certificate that is e.g. listed on the official PKI website  or
99       by some other means.
100
101       The  stored  certificate files in DER format can be overwritten by PEM-
102       encoded versions with:
103
104       pki --estca --options est.opt --caout myca.crt --outform pem --force
105
106       A CA certificate bundle in PEM format is written to stdout:
107
108       pki --estca --options est.opt --outform pem > cacerts.pem
109

NAME

SYNOPSIS

DESCRIPTION

OPTIONS

EXAMPLES

SEE ALSO