mirror of
https://blitiri.com.ar/repos/chasquid
synced 2026-01-08 17:51:57 +00:00
etc: Mention certificate requirements in the documentation
chasquid needs at least one certificate in order to start, to prevent accidental misconfigurations. This patch documents this in etc/chasquid/README, and while at it fixes a minor terminology issue. Thanks to Martin Ferrari for the bug report!
This commit is contained in:
@@ -19,8 +19,11 @@ This directory contains chasquid's configuration.
|
|||||||
Note the certs/ directory matches certbot's structure, so if you use it you
|
Note the certs/ directory matches certbot's structure, so if you use it you
|
||||||
can just symlink to /etc/letsencrypt/live.
|
can just symlink to /etc/letsencrypt/live.
|
||||||
|
|
||||||
|
You need at least one certificate, or the server will refuse to start.
|
||||||
|
Ideally there should be a certificate for each DNS name pointing to you.
|
||||||
|
|
||||||
Make sure the user you use to run chasquid under ("mail" in the example
|
Make sure the user you use to run chasquid under ("mail" in the example
|
||||||
config) can access the certificates and private keys.
|
systemd files) can access the certificates and private keys.
|
||||||
|
|
||||||
|
|
||||||
The user databases can be created and edited with the chasquid-util tool.
|
The user databases can be created and edited with the chasquid-util tool.
|
||||||
|
|||||||
Reference in New Issue
Block a user