From 4d3bea73fa0f5fc769a0bcb4b3e6497a5b6401fe Mon Sep 17 00:00:00 2001 From: Johann150 Date: Sat, 21 Feb 2026 17:03:57 +0100 Subject: [PATCH] using IP addresses for certs might be broken closes #345 --- README.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 678a1db..df18001 100644 --- a/README.md +++ b/README.md @@ -83,7 +83,11 @@ When a client requests the URL `gemini://example.com/foo/bar`, Agate will respon ### Automatic Certificate generation -If the `--hostname` argument is used, Agate will generate keys and self signed certificates for each hostname specified. For Gemini it is recommended by the specification to use self signed certificates because Gemini uses the TOFU (Trust on first use) principle for certificates. Because of this, the generated certificates will also have a long expiration time of `4096-01-01`. +If the `--hostname` argument is used, Agate will generate keys and self signed certificates for each hostname specified. +Please note that using an IP address for certificates is not (intentionally) supported. + +For Gemini it is recommended by the specification to use self signed certificates because Gemini uses the TOFU (Trust on first use) principle for certificates. +Because of this, the generated certificates will also have a long expiration time of `4096-01-01`. For manual configuration of keys and certificates see the [section on certificates](#certificates) below.