diff options
author | Marek Paśnikowski <marek@marekpasnikowski.pl> | 2025-05-29 10:44:39 +0200 |
---|---|---|
committer | Marek Paśnikowski <marek@marekpasnikowski.pl> | 2025-05-29 10:44:39 +0200 |
commit | 38c7690a5d662730a7cf096995fc1bcfff511d91 (patch) | |
tree | 0e87df301d13ddd0bb2aa822a86e6feafd45689c /deployment/systems/ayase.scm | |
parent | 18448e8e862015cbe5680ec20db0b48c6518e6d5 (diff) |
aisaka: use a Let’s Encrypt certificate for the test subdomain
The prototype of the client certificate authentication is suboptimal.
The use of a private certificate authority for server authentication causes unnecessary security warnings when loading the subdomain with an unauthenticated browser.
Any browser in its default configuration has no right to understand the private certificate authority used for the client and server certificates.
It is possible to mix Let’s Encrypt certificates with a private certificate authority to implement the authentication.
None of the previously found client authentication guides mentioned that server authentication can use an authority chain different to client authentication.
This change takes advantage of this separation of concerns by using a Let’s Encrypt certificate for the test subdomain server, while keeping the private certificate for client authentication.
Diffstat (limited to 'deployment/systems/ayase.scm')
0 files changed, 0 insertions, 0 deletions