From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: "Alexander A. Klimov" <grandmaster@al2klimov.de>
Cc: paulburton@kernel.org, linux-mips@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mips: Replace HTTP links with HTTPS ones
Date: Thu, 16 Jul 2020 11:55:01 +0200 [thread overview]
Message-ID: <20200716095501.GE8455@alpha.franken.de> (raw)
In-Reply-To: <20200714191226.48652-1-grandmaster@al2klimov.de>
On Tue, Jul 14, 2020 at 09:12:26PM +0200, Alexander A. Klimov wrote:
> 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 neither `\bgnu\.org/license`, nor `\bmozilla\.org/MPL\b`:
> 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>
> ---
> arch/mips/Kconfig | 2 +-
> arch/mips/include/asm/war.h | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2020-07-16 10:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 8:52 [PATCH] MIPS: Replace HTTP links with HTTPS ones Alexander A. Klimov
2020-07-14 6:45 ` Jiaxun Yang
2020-07-14 19:12 ` [PATCH] mips: " Alexander A. Klimov
2020-07-16 9:55 ` Thomas Bogendoerfer [this message]
[not found] ` <CAHiYmc7ax=A=Tb59wh4+yHx=2MEKc3G==tun5nsefbKvsceBHg@mail.gmail.com>
2020-07-16 13:56 ` [PATCH] MIPS: " Thomas Bogendoerfer
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=20200716095501.GE8455@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=grandmaster@al2klimov.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=paulburton@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).