From b1a29d8194115842e5b808563cfb176d037c0ddb Mon Sep 17 00:00:00 2001 From: Alberto Bertogli Date: Tue, 22 Nov 2016 20:43:07 +0000 Subject: [PATCH] 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! --- etc/chasquid/README | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/etc/chasquid/README b/etc/chasquid/README index 82ac8ac..9f0df00 100644 --- a/etc/chasquid/README +++ b/etc/chasquid/README @@ -19,8 +19,11 @@ This directory contains chasquid's configuration. Note the certs/ directory matches certbot's structure, so if you use it you 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 -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.