YGGverse/agate
1
0
Fork 0
mirror of https://github.com/YGGverse/agate.git synced 2026-04-08 20:45:29 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

using IP addresses for certs might be broken

Browse source 
closes #345
This commit is contained in:
Johann150 2026-02-21 17:03:57 +01:00
parent 28e7ca6b92
commit 4d3bea73fa
No known key found for this signature in database
GPG key ID: 9EE6577A2A06F8F1
1 changed files with 5 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

6
README.md
View file

@ -83,7 +83,11 @@ When a client requests the URL `gemini://example.com/foo/bar`, Agate will respon
### Automatic Certificate generation ### 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. For manual configuration of keys and certificates see the [section on certificates](#certificates) below.