From: "Alexander A. Klimov" <grandmaster@al2klimov.de>
To: sudeep.dutt@intel.com, ashutosh.dixit@intel.com, arnd@arndb.de,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org
Cc: "Alexander A. Klimov" <grandmaster@al2klimov.de>
Subject: [PATCH] Replace HTTP links with HTTPS ones: Intel mic drivers
Date: Wed, 8 Jul 2020 04:50:13 +0200 [thread overview]
Message-ID: <20200708025013.57804-1-grandmaster@al2klimov.de> (raw)
Rationale:
Reduces attack surface on kernel devs opening the links for MITM
as HTTPS traffic is much harder to manipulate.
Deterministic algorithm:
For each file:
If not .svg:
For each line:
If doesn't contain `\bxmlns\b`:
For each link, `\bhttp://[^# \t\r\n]*(?:\w|/)`:
If both the HTTP and HTTPS versions
return 200 OK and serve the same content:
Replace HTTP with HTTPS.
Signed-off-by: Alexander A. Klimov <grandmaster@al2klimov.de>
---
Continuing my work started at 93431e0607e5.
See also: git log --oneline '--author=Alexander A. Klimov <grandmaster@al2klimov.de>' v5.7..master
If there are any URLs to be removed completely or at least not HTTPSified:
Just clearly say so and I'll *undo my change*.
See also: https://lkml.org/lkml/2020/6/27/64
If there are any valid, but yet not changed URLs:
See: https://lkml.org/lkml/2020/6/26/837
If you apply the patch, please let me know.
Rationale:
I'd like not to submit patches much faster than you maintainers apply them.
drivers/misc/mic/Kconfig | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/drivers/misc/mic/Kconfig b/drivers/misc/mic/Kconfig
index 8f201d019f5a..a20202df8ce2 100644
--- a/drivers/misc/mic/Kconfig
+++ b/drivers/misc/mic/Kconfig
@@ -14,7 +14,7 @@ config INTEL_MIC_BUS
More information about the Intel MIC family as well as the Linux
OS and tools for MIC to use with this driver are available from
- <http://software.intel.com/en-us/mic-developer>.
+ <https://software.intel.com/en-us/mic-developer>.
config SCIF_BUS
tristate "SCIF Bus Driver"
@@ -29,7 +29,7 @@ config SCIF_BUS
More information about the Intel MIC family as well as the Linux
OS and tools for MIC to use with this driver are available from
- <http://software.intel.com/en-us/mic-developer>.
+ <https://software.intel.com/en-us/mic-developer>.
config VOP_BUS
tristate "VOP Bus Driver"
@@ -43,7 +43,7 @@ config VOP_BUS
More information about the Intel MIC family as well as the Linux
OS and tools for MIC to use with this driver are available from
- <http://software.intel.com/en-us/mic-developer>.
+ <https://software.intel.com/en-us/mic-developer>.
config INTEL_MIC_HOST
tristate "Intel MIC Host Driver"
@@ -61,7 +61,7 @@ config INTEL_MIC_HOST
More information about the Intel MIC family as well as the Linux
OS and tools for MIC to use with this driver are available from
- <http://software.intel.com/en-us/mic-developer>.
+ <https://software.intel.com/en-us/mic-developer>.
config INTEL_MIC_CARD
tristate "Intel MIC Card Driver"
@@ -78,7 +78,7 @@ config INTEL_MIC_CARD
say M (recommended) or Y, else say N. If unsure say N.
For more information see
- <http://software.intel.com/en-us/mic-developer>.
+ <https://software.intel.com/en-us/mic-developer>.
config SCIF
tristate "SCIF Driver"
@@ -96,7 +96,7 @@ config SCIF
More information about the Intel MIC family as well as the Linux
OS and tools for MIC to use with this driver are available from
- <http://software.intel.com/en-us/mic-developer>.
+ <https://software.intel.com/en-us/mic-developer>.
config MIC_COSM
tristate "Intel MIC Coprocessor State Management (COSM) Drivers"
@@ -112,7 +112,7 @@ config MIC_COSM
More information about the Intel MIC family as well as the Linux
OS and tools for MIC to use with this driver are available from
- <http://software.intel.com/en-us/mic-developer>.
+ <https://software.intel.com/en-us/mic-developer>.
config VOP
tristate "VOP Driver"
@@ -131,6 +131,6 @@ config VOP
More information about the Intel MIC family as well as the Linux
OS and tools for MIC to use with this driver are available from
- <http://software.intel.com/en-us/mic-developer>.
+ <https://software.intel.com/en-us/mic-developer>.
endmenu
--
2.27.0
reply other threads:[~2020-07-08 2:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200708025013.57804-1-grandmaster@al2klimov.de \
--to=grandmaster@al2klimov.de \
--cc=arnd@arndb.de \
--cc=ashutosh.dixit@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sudeep.dutt@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).