Age | Commit message (Collapse) | Author |
|
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.
|
|
|
|
|
|
This reverts commit ba64ebfe587f05c734f24ace507d22629d350cd8.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The indirect bindings force the Sovereign channel to unnecessarily depend on Nonguix.
|
|
The indirect bindings force the Sovereign channel to unnecessarily depend on Nonguix.
|
|
|