From: Daniel Stenberg <daniel@haxx.se>
Date: Thu, 31 May 2018 09:11:38 +0000 (+0200)
Subject: libcurl-security.3: refer to URL instead of in-source markdown file
X-Git-Tag: curl-7_61_0~103
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=5f07fca8f75243eb8e9831228ea379b3dc9cd7b0;p=thirdparty%2Fcurl.git

libcurl-security.3: refer to URL instead of in-source markdown file
---

diff --git a/docs/libcurl/libcurl-security.3 b/docs/libcurl/libcurl-security.3
index 25ae400fe5..f5f510e2c1 100644
--- a/docs/libcurl/libcurl-security.3
+++ b/docs/libcurl/libcurl-security.3
@@ -317,8 +317,8 @@ one. HTTPS without validated certificates is potentially as insecure as a
 plain HTTP connection.
 .SH "Report Security Problems"
 Should you detect or just suspect a security problem in libcurl or curl,
-contact the project curl security team immediately. See the separate
-SECURITY.md document for details.
+contact the project curl security team immediately. See
+https://curl.haxx.se/dev/secprocess.html for details.
 .SH "Showing What You Do"
 Relatedly, be aware that in situations when you have problems with libcurl and
 ask someone for help, everything you reveal in order to get best possible help