starred/dehydrated
1
0
Fork 0
mirror of https://github.com/dehydrated-io/dehydrated.git synced 2026-03-17 23:03:47 +01:00
Code Issues 79 Packages Projects Releases 10 Wiki Activity

moved deploy_challenge to earlier loop so it works with multiple challenge tokens on the same identifier (important for wildcard certificate), fixed array-name, removed hook-chain warning

Browse Source
This commit is contained in:
Lukas Schauer
2018-01-28 19:43:03 +01:00
parent 471899b4d8
commit afba7c694c
3 changed files with 13 additions and 29 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
docs/hook_chain.md
View File

@@ -60,15 +60,3 @@ HOOK: clean_challenge lukas.im blablabla blablabla.supersecure www.lukas.im blub
HOOK: deploy_cert lukas.im /etc/dehydrated/certs/lukas.im/privkey.pem /etc/dehydrated/certs/lukas.im/cert.pem /etc/dehydrated/certs/lukas.im/fullchain.pem /etc/dehydrated/certs/lukas.im/chain.pem 1460152408
+ Done!
```
# Problem with wildcard certificates
For wildcard certificates the upper level domain is used for verification, e.g.
`*.foo.example.com` will be verified at `foo.example.com`.
In cases where both `foo.example.com` and `*.foo.example.com` would have to be
validated there would be a conflict since both will have different tokens but
both are expected to be resolved under `_acme-challenge.foo.example.com`.
If dehydrated detects this kind of configuration it will automatically fall back
to non-chaining behaviour (until the next certificate).