From: "Alexander A. Klimov" <grandmaster@al2klimov.de>
To: jrv@vanzandt.mv.com, arnd@arndb.de, gregkh@linuxfoundation.org,
blinux-list@redhat.com, linux-kernel@vger.kernel.org
Cc: "Alexander A. Klimov" <grandmaster@al2klimov.de>
Subject: [PATCH] Replace HTTP links with HTTPS ones: Doubletalk driver
Date: Sun, 5 Jul 2020 13:17:48 +0200 [thread overview]
Message-ID: <20200705111748.25591-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.
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
drivers/char/dtlk.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/char/dtlk.c b/drivers/char/dtlk.c
index 6946c1cad9f6..5ec8185cb76b 100644
--- a/drivers/char/dtlk.c
+++ b/drivers/char/dtlk.c
@@ -13,7 +13,7 @@
*/
/* This driver is for the DoubleTalk PC, a speech synthesizer
- manufactured by RC Systems (http://www.rcsys.com/). It was written
+ manufactured by RC Systems (https://www.rcsys.com/). It was written
based on documentation in their User's Manual file and Developer's
Tools disk.
--
2.27.0
reply other threads:[~2020-07-05 11:18 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=20200705111748.25591-1-grandmaster@al2klimov.de \
--to=grandmaster@al2klimov.de \
--cc=arnd@arndb.de \
--cc=blinux-list@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=jrv@vanzandt.mv.com \
--cc=linux-kernel@vger.kernel.org \
/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).