From: James Morris <jmorris@namei.org>
To: "Alexander A. Klimov" <grandmaster@al2klimov.de>
Cc: serge@hallyn.com, john.johansen@canonical.com,
zohar@linux.ibm.com, dmitry.kasatkin@gmail.com,
dhowells@redhat.com, jarkko.sakkinen@linux.intel.com,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-integrity@vger.kernel.org,
keyrings@vger.kernel.org
Subject: Re: [PATCH] Replace HTTP links with HTTPS ones: security
Date: Tue, 07 Jul 2020 20:28:31 +0000 [thread overview]
Message-ID: <alpine.LRH.2.21.2007080628020.1849@namei.org> (raw)
In-Reply-To: <20200705214512.28498-1-grandmaster@al2klimov.de>
On Sun, 5 Jul 2020, 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 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>
Thanks.
Applied to
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git next-general
--
James Morris
<jmorris@namei.org>
WARNING: multiple messages have this Message-ID (diff)
From: James Morris <jmorris@namei.org>
To: "Alexander A. Klimov" <grandmaster@al2klimov.de>
Cc: serge@hallyn.com, john.johansen@canonical.com,
zohar@linux.ibm.com, dmitry.kasatkin@gmail.com,
dhowells@redhat.com, jarkko.sakkinen@linux.intel.com,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-integrity@vger.kernel.org,
keyrings@vger.kernel.org
Subject: Re: [PATCH] Replace HTTP links with HTTPS ones: security
Date: Wed, 8 Jul 2020 06:28:31 +1000 (AEST) [thread overview]
Message-ID: <alpine.LRH.2.21.2007080628020.1849@namei.org> (raw)
In-Reply-To: <20200705214512.28498-1-grandmaster@al2klimov.de>
On Sun, 5 Jul 2020, 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 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>
Thanks.
Applied to
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git next-general
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2020-07-07 20:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-05 21:45 [PATCH] Replace HTTP links with HTTPS ones: security Alexander A. Klimov
2020-07-05 21:45 ` Alexander A. Klimov
2020-07-05 21:59 ` John Johansen
2020-07-05 21:59 ` John Johansen
2020-07-07 20:28 ` James Morris [this message]
2020-07-07 20:28 ` James Morris
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=alpine.LRH.2.21.2007080628020.1849@namei.org \
--to=jmorris@namei.org \
--cc=dhowells@redhat.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=grandmaster@al2klimov.de \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=john.johansen@canonical.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=serge@hallyn.com \
--cc=zohar@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.