Lines Matching full:pem

14 provided in PEM format. Aside from the core fields, the certificates
54 # certtool --generate-privkey > ca-key.pem
67 --load-privkey ca-key.pem \
69 --outfile ca-cert.pem
74 be used for signing other keys. The generated ``ca-cert.pem`` file
76 support in the VNC server. The ``ca-key.pem`` must not be
124 # certtool --generate-privkey > server-hostNNN-key.pem
126 --load-ca-certificate ca-cert.pem \
127 --load-ca-privkey ca-key.pem \
128 --load-privkey server-hostNNN-key.pem \
130 --outfile server-hostNNN-cert.pem
141 The ``server-hostNNN-key.pem`` and ``server-hostNNN-cert.pem`` files
143 generated, and renamed to ``server-key.pem`` and ``server-cert.pem``
145 ``server-key.pem`` file is security sensitive and should be kept
177 # certtool --generate-privkey > client-hostNNN-key.pem
179 --load-ca-certificate ca-cert.pem \
180 --load-ca-privkey ca-key.pem \
181 --load-privkey client-hostNNN-key.pem \
183 --outfile client-hostNNN-cert.pem
194 The ``client-hostNNN-key.pem`` and ``client-hostNNN-cert.pem`` files
196 generated, and renamed to ``client-key.pem`` and ``client-cert.pem``
198 ``client-key.pem`` file is security sensitive and should be kept
228 # certtool --generate-privkey > both-hostNNN-key.pem
230 --load-ca-certificate ca-cert.pem \
231 --load-ca-privkey ca-key.pem \
232 --load-privkey both-hostNNN-key.pem \
234 --outfile both-hostNNN-cert.pem
236 When copying the PEM files to the target host, save them twice, once as
237 ``server-cert.pem`` and ``server-key.pem``, and again as
238 ``client-cert.pem`` and ``client-key.pem``.
257 contain files with the names mentioned previously, ``ca-cert.pem``,
258 ``server-key.pem``, ``server-cert.pem``, ``client-key.pem`` and
259 ``client-cert.pem`` as appropriate. It is also possible to include a set
261 ``dh-params.pem``, which can be created using the
266 used for a network client or server, and determines which PEM files are