diff options
| -rw-r--r-- | content/blog/2020/email-server-extras.md | 6 | ||||
| -rw-r--r-- | templates/page.html | 7 |
2 files changed, 9 insertions, 4 deletions
diff --git a/content/blog/2020/email-server-extras.md b/content/blog/2020/email-server-extras.md index 47d826e..2af52a4 100644 --- a/content/blog/2020/email-server-extras.md +++ b/content/blog/2020/email-server-extras.md @@ -218,7 +218,7 @@ You can configure OpenSMTPD to request a client certificate for sending emails, as a second factor for authentication. -#### Creating certificates +#### Certificates We need to start with some cryptography to create and verify certificates. I recommend that you do all of this on your trusted *client* device, @@ -268,7 +268,7 @@ If you want to multiple client certificates, just repeat the last few steps for each one. -#### Server configuration +#### Server OpenSMTPD needs to verify the validity of client certificates using the CA's public certificate, so you should copy that @@ -290,7 +290,7 @@ The magic word here is "`verify`", which tells OpenSMTPD to ask for a client certificate and to verify it using the given CA. -#### Client configuration +#### Client Now you won't be able to send emails if your client doesn't present its certificate to the server! diff --git a/templates/page.html b/templates/page.html index 2144e35..b06039f 100644 --- a/templates/page.html +++ b/templates/page.html @@ -9,7 +9,12 @@ <li><a href="{{ h2.permalink | safe }}">{{ h2.title }}</a> {% if h2.children %} <ul>{% for h3 in h2.children %} - <li><a href="{{ h3.permalink | safe }}">{{ h3.title }}</a></li> + <li><a href="{{ h3.permalink | safe }}">{{ h3.title }}</a> + {% if h3.children %} + <ul>{% for h4 in h3.children %} + <li><a href="{{ h4.permalink | safe }}">{{ h4.title }}</a> + {% endfor %}</ul> + {% endif %}</li> {% endfor %}</ul> {% endif %}</li> {% endfor %}</ul> |