summaryrefslogtreecommitdiffstats
path: root/docs/reference/plugins/validation
diff options
context:
space:
mode:
authorWouterTinus <wouter.tinus@gmail.com>2019-08-26 07:06:41 +0200
committerWouterTinus <wouter.tinus@gmail.com>2019-08-26 07:06:41 +0200
commit833289e1538f868166a5dd5f9613893e770e8c93 (patch)
tree806ee04ac9cf7dfeabdd87ff3905d917e3ff5f48 /docs/reference/plugins/validation
parenta60811a02dc9eaccf233946557b3e00e01bb3176 (diff)
downloadletsencrypt-win-simple-833289e1538f868166a5dd5f9613893e770e8c93.zip
letsencrypt-win-simple-833289e1538f868166a5dd5f9613893e770e8c93.tar.gz
letsencrypt-win-simple-833289e1538f868166a5dd5f9613893e770e8c93.tar.bz2
adopt bugfixes fluentcommandlineparser
Diffstat (limited to 'docs/reference/plugins/validation')
-rw-r--r--docs/reference/plugins/validation/http/index.md3
-rw-r--r--docs/reference/plugins/validation/http/selfhosting.md7
-rw-r--r--docs/reference/plugins/validation/index.md8
3 files changed, 15 insertions, 3 deletions
diff --git a/docs/reference/plugins/validation/http/index.md b/docs/reference/plugins/validation/http/index.md
index 71a67b9..41a4f3d 100644
--- a/docs/reference/plugins/validation/http/index.md
+++ b/docs/reference/plugins/validation/http/index.md
@@ -10,8 +10,9 @@ but for the sake of this explanation it will suffice).
- The client has to make sure that when the ACME server makes a request
to `http://sub.example.com/.well-known/acme-challenge/x`, the answer will be exactly `y`.
- The validation request is *always* made to port 80, that cannot be changed.
+- Let's Encrypt **does** follow 301/302 redirects
- There may be more than one validation request for the same token, e.g. from
different locations or different protocols (IPv4/IPv6).
-- Let's Encrypt does *not* disclose the source locations of these requests, which
+- Let's Encrypt does **not** disclose the source locations of these requests, which
effectively means that the domain has to be accessible for the public,
at least for the duration of the validation. \ No newline at end of file
diff --git a/docs/reference/plugins/validation/http/selfhosting.md b/docs/reference/plugins/validation/http/selfhosting.md
index 649c248..6ce5081 100644
--- a/docs/reference/plugins/validation/http/selfhosting.md
+++ b/docs/reference/plugins/validation/http/selfhosting.md
@@ -10,5 +10,10 @@ Not all software supports this port sharing feature though. If you get errors
telling you that the listener cannot be started, please look for another
validation method.
+## Non-default port
+Even though Let's Encrypt will always send validation requests to port 80,
+you may internally proxy, NAT or redirect that to another port. Using the
+`--validationport` switch you can tell the plugin to listen to a specific port.
+
## Unattended
-`[--validation selfhosting]` \ No newline at end of file
+`[--validation selfhosting] [--validationport 8080]` \ No newline at end of file
diff --git a/docs/reference/plugins/validation/index.md b/docs/reference/plugins/validation/index.md
index 2f6d14f..f5b8f0d 100644
--- a/docs/reference/plugins/validation/index.md
+++ b/docs/reference/plugins/validation/index.md
@@ -2,6 +2,8 @@
sidebar: reference
---
+# Validation plugins
+
A validation plugin is responsible for providing the ACME server with proof that you own the identifiers
(host names) that you want to create a certificate for. The
[ACMEv2 protocol](https://tools.ietf.org/html/draft-ietf-acme-acme-18) defines different challenge types,
@@ -13,4 +15,8 @@ For wildcard identifiers, only DNS validation is accepted by Let's Encrypt.
Other challenge types are not supported for various reasons:
- `TLS-ALPN-01` - under investigation (see [#990](https://github.com/PKISharp/win-acme/issues/990))
- `TLS-SNI-01/-02` - deprecated and all but removed
-- `PROOFOFPOSSESSION-01` - unknown \ No newline at end of file
+- `PROOFOFPOSSESSION-01` - unknown
+
+## Default
+
+By default, the [self-hosting plugin](/win-acme/reference/plugins/validation/http/selfhosting) is used. \ No newline at end of file