Self sign-up has been disabled due to increased spam activity. If you want to get access, please send an email to a project owner (preferred) or at gitlab(at)nic(dot)cz. We apologize for the inconvenience.
@@ -13,11 +13,10 @@ Their usage is described below.
...
@@ -13,11 +13,10 @@ Their usage is described below.
>>>
>>>
**WARNING:** Self-signed certificates are of course not considered trustworthy
**WARNING:** Self-signed certificates are of course not considered trustworthy
by common web browsers and operating systems, so they are only suitable for
by web browsers and operating systems, so they are only suitable for testing.
testing.
>>>
>>>
## Certification Authority (CA)
## Certification Authority
The generated server and client certificates have to be signed by a Certificate Authority (CA). For production uses, a trusted CA should always be used. For testing purposes, though, a self-signed CA-like certificate will do. The easiest, but least secure, way is to use the pre-generated CA-like certificate and private key from the files `ca.pem` and `ca.key` available from the [JetConf](https://gitlab.labs.nic.cz/labs/jetconf) repository (subdirectory `utils/cert_gen`). Alternatively, the CA-like certificate and key can be generated using the procedure below.
The generated server and client certificates have to be signed by a Certificate Authority (CA). For production uses, a trusted CA should always be used. For testing purposes, though, a self-signed CA-like certificate will do. The easiest, but least secure, way is to use the pre-generated CA-like certificate and private key from the files `ca.pem` and `ca.key` available from the [JetConf](https://gitlab.labs.nic.cz/labs/jetconf) repository (subdirectory `utils/cert_gen`). Alternatively, the CA-like certificate and key can be generated using the procedure below.