# the service is protected by client's certificate verification
# mechanism. Before using this configuration a server administrator
# must generate server certificate and private key as well as
-# the certifiate authority (CA). The clients' certificates must
+# the certificate authority (CA). The clients' certificates must
# be signed by the CA.
#
-# Note that the steps provided below to generate and setup certifcates
+# Note that the steps provided below to generate and setup certificates
# are provided as an example for testing purposes only. Always
# consider best known security measures to protect your production
# environment.
# openssl req -new -x509 -days 365 -key ca.key -out ca.crt
#
#
-# The client certifcate needs to be generated and signed:
+# The client certificate needs to be generated and signed:
#
# openssl genrsa -des3 -out kea-client.key 4096
# openssl req -new -key kea-client.key -out kea-client.csr
# the service is protected by client's certificate verification
# mechanism. Before using this configuration a server administrator
# must generate server certificate and private key as well as
-# the certifiate authority (CA). The clients' certificates must
+# the certificate authority (CA). The clients' certificates must
# be signed by the CA.
#
-# Note that the steps provided below to generate and setup certifcates
+# Note that the steps provided below to generate and setup certificates
# are provided as an example for testing purposes only. Always
# consider best known security measures to protect your production
# environment.
a reverse proxy server is also often used for authentication of the
controlling clients. In this case, the client must present a valid
certificate when it connects via reverse proxy. The proxy server
- authenticates the client by checking if the presented certifcate is
+ authenticates the client by checking if the presented certificate is
signed by the certificate authority used by the server.</para>
<para>To illustrate this, we provide a sample configuration for the