docs: link to the website versions instead of markdowns

... to make the links work when the markdown is converted to webpages on
https://curl.se

Reported-by: Maurício Meneghini Fauth
Fixes https://github.com/curl/curl-www/issues/272
Closes #11569

diff --git a/docs/BUG-BOUNTY.md b/docs/BUG-BOUNTY.md
index aa8ee8957273c38358e54fe000e6756f9e7164e0..3714efda524550bfad9294019edbcf27560db2a9 100644 (file)
--- a/docs/BUG-BOUNTY.md
+++ b/docs/BUG-BOUNTY.md
@@ -11,8 +11,8 @@ HackerOne program](https://hackerone.com/curl).
 
 After you have reported a security issue, it has been deemed credible, and a
 patch and advisory has been made public, you may be eligible for a bounty from
-this program. See the [SECURITY-PROCESS](SECURITY-PROCESS.md) document for how
-we work with security issues.
+this program. See the [Security Process](https://curl.se/dev/secprocess.html)
+document for how we work with security issues.
 
 ## What are the reward amounts?
 

diff --git a/docs/SECURITY-ADVISORY.md b/docs/SECURITY-ADVISORY.md
index c2d13c92316499ded7c6d34f6a4a9336ebb62c0f..37083cd3c52563f471878afbe066d7807b9d6210 100644 (file)
--- a/docs/SECURITY-ADVISORY.md
+++ b/docs/SECURITY-ADVISORY.md
@@ -1,10 +1,10 @@
 # Anatomy of a curl security advisory
 
-As described in the `SECURITY-PROCESS.md` document, when a security
-vulnerability has been reported to the project and confirmed, we author an
-advisory document for for the issue. It should ideally be written in
-cooperation with the reporter to make sure all the angles and details of the
-problem are gathered and described correctly and succinctly.
+As described in the [Security Process](https://curl.se/dev/secprocess.html)
+document, when a security vulnerability has been reported to the project and
+confirmed, we author an advisory document for for the issue. It should ideally
+be written in cooperation with the reporter to make sure all the angles and
+details of the problem are gathered and described correctly and succinctly.
 
 ## New document
 

diff --git a/docs/SECURITY-PROCESS.md b/docs/SECURITY-PROCESS.md
index e553507a4cd34841d4d724df3cbcd791eb5201ab..64123edd451bc807bff4ab46ce3e5126e2a3d05d 100644 (file)
--- a/docs/SECURITY-PROCESS.md
+++ b/docs/SECURITY-PROCESS.md
@@ -56,7 +56,8 @@ announcement.
   problem is, its impact, which versions it affects, solutions or workarounds,
   when the release is out and make sure to credit all contributors properly.
   Figure out the CWE (Common Weakness Enumeration) number for the flaw. See
-  [SECURITY-ADVISORY](SECURITY-ADVISORY.md) for help on creating the advisory.
+  [SECURITY-ADVISORY](https://curl.se/dev/advisory.html) for help on creating
+  the advisory.
 
 - Request a CVE number from
   [HackerOne](https://docs.hackerone.com/programs/cve-requests.html)