You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: source/admin_manual/ssl/certificate_creation.rst
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ The only way to be fully secure is to import the SSL certificate to client's (or
14
14
Self-signed certificate creation
15
15
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
16
16
17
-
Dovecot includes a script to build self-signed SSL certificates using OpenSSL. In the source distribution this exists in https://dovecot.org/tools/mkcert.sh. Binary installations usually create the certificate automatically when installing Dovecot and don't include the script.
17
+
Dovecot includes a script to build self-signed SSL certificates using OpenSSL (see https://github.com/dovecot/tools/blob/main/mkcert.sh). Binary installations usually create the certificate automatically when installing Dovecot and don't include the script.
18
18
19
19
The SSL certificate's configuration is taken from https://dovecot.org/doc/dovecot-openssl.cnf file. Modify the file before running mkcert.sh. Especially important field is the CN (Common Name) field, which should contain your server's host name. The clients will verify that the CN matches the connected host name, otherwise they'll say the certificate is invalid. It's also possible to use wildcards (eg. \*.domain.com) in the host name. They should work with most clients.
0 commit comments