From 0939e9cc65585787fb866eba975224651c057322 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lo=C3=AFc=20Dachary?= Date: Thu, 9 Mar 2023 07:29:40 +0100 Subject: [PATCH] fully qualified link to issue --- v1.19/admin/database-preparation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/v1.19/admin/database-preparation.md b/v1.19/admin/database-preparation.md index 335b39a4..3ee8a3ea 100644 --- a/v1.19/admin/database-preparation.md +++ b/v1.19/admin/database-preparation.md @@ -240,7 +240,7 @@ The PostgreSQL driver used by Forgejo supports two-way TLS. In two-way TLS, both ### MySQL -While the MySQL driver used by Forgejo also supports two-way TLS, Forgejo currently supports only one-way TLS. See issue #10828 for details. +While the MySQL driver used by Forgejo also supports two-way TLS, Forgejo currently supports only one-way TLS. See the "Add TLS File Path Options for MySQL Database Connection](https://github.com/go-gitea/gitea/issues/10828)" issue for details. In one-way TLS, the database client verifies the certificate sent from server during the connection handshake, and the server assumes that the connected client is legitimate, since client certificate verification doesn't take place.