# HG changeset patch
# User Kim Alvefur <zash@zash.se>
# Date 1612645958 -3600
# Node ID 0bc3acf37428953541e02d17ca21101fba96c4ec
# Parent  9525c4b4e5de8a62e40b7fb766f54c25950261e2
core.certmanager: Add comments explaining the 'verifyext' TLS settings

Thanks to debacle for reminding me, in the context of mod_auth_ccert

I wonder if we still need lsec_ignore_purpose, Let's Encrypt seems to
include both client and server purposes in certs.

diff -r 9525c4b4e5de -r 0bc3acf37428 core/certmanager.lua
--- a/core/certmanager.lua	Sat Feb 06 21:40:21 2021 +0100
+++ b/core/certmanager.lua	Sat Feb 06 22:12:38 2021 +0100
@@ -118,7 +118,10 @@
 		single_dh_use = luasec_has.options.single_dh_use;
 		single_ecdh_use = luasec_has.options.single_ecdh_use;
 	};
-	verifyext = { "lsec_continue", "lsec_ignore_purpose" };
+	verifyext = {
+		"lsec_continue", -- Continue past certificate verification errors
+		"lsec_ignore_purpose", -- Validate client certificates as if they were server certificates
+	};
 	curve = luasec_has.algorithms.ec and not luasec_has.capabilities.curves_list and "secp384r1";
 	curveslist = {
 		"X25519",