From e0d05e00c6831222d27cbd1ffee94f0ad3c901d9 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 13 Apr 2021 19:58:35 -0400 Subject: [PATCH] comment --- ...mment_1_39af4df2a16e363f93f75a7a57af048c._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/forum/Disable_ssl_verification__63__/comment_1_39af4df2a16e363f93f75a7a57af048c._comment diff --git a/doc/forum/Disable_ssl_verification__63__/comment_1_39af4df2a16e363f93f75a7a57af048c._comment b/doc/forum/Disable_ssl_verification__63__/comment_1_39af4df2a16e363f93f75a7a57af048c._comment new file mode 100644 index 0000000000..92261c9e12 --- /dev/null +++ b/doc/forum/Disable_ssl_verification__63__/comment_1_39af4df2a16e363f93f75a7a57af048c._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2021-04-13T23:55:12Z" + content=""" +There is not currently a way to do this, other than of course to use http +rather than https. + +I'm not sure if it's even possible to implement it; the underlying tls +library would would need a way to configure it to be insecure, and that is +rather in tension with the actual purpose of a tls library. +"""]]