From: Alexandre Torgue <alexandre.torgue@st.com>
To: "Alexander A. Klimov" <grandmaster@al2klimov.de>,
<linux@armlinux.org.uk>, <mcoquelin.stm32@gmail.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] ARM: STM32: Replace HTTP links with HTTPS ones
Date: Fri, 28 Aug 2020 09:04:31 +0200 [thread overview]
Message-ID: <f6d9e6d7-60ea-85c3-9291-c7c01befc7ef@st.com> (raw)
In-Reply-To: <20200722192046.69334-1-grandmaster@al2klimov.de>
Hi Alexander
On 7/22/20 9:20 PM, 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>
> ---
Applied on stm32-next.
Thanks.
Alex
WARNING: multiple messages have this Message-ID (diff)
From: Alexandre Torgue <alexandre.torgue@st.com>
To: "Alexander A. Klimov" <grandmaster@al2klimov.de>,
<linux@armlinux.org.uk>, <mcoquelin.stm32@gmail.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] ARM: STM32: Replace HTTP links with HTTPS ones
Date: Fri, 28 Aug 2020 09:04:31 +0200 [thread overview]
Message-ID: <f6d9e6d7-60ea-85c3-9291-c7c01befc7ef@st.com> (raw)
In-Reply-To: <20200722192046.69334-1-grandmaster@al2klimov.de>
Hi Alexander
On 7/22/20 9:20 PM, 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>
> ---
Applied on stm32-next.
Thanks.
Alex
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-08-28 7:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-19 9:49 [PATCH for v5.9] ARM: STM32: Replace HTTP links with HTTPS ones Alexander A. Klimov
2020-07-19 9:49 ` Alexander A. Klimov
2020-07-21 8:49 ` Alexandre Torgue
2020-07-21 8:49 ` Alexandre Torgue
2020-07-21 17:49 ` Alexander A. Klimov
2020-07-21 17:49 ` Alexander A. Klimov
2020-07-22 7:06 ` Alexandre Torgue
2020-07-22 7:06 ` Alexandre Torgue
2020-07-22 7:11 ` Herbert Xu
2020-07-22 7:11 ` Herbert Xu
2020-07-22 19:20 ` [PATCH v2] " Alexander A. Klimov
2020-07-22 19:20 ` Alexander A. Klimov
2020-08-28 7:04 ` Alexandre Torgue [this message]
2020-08-28 7:04 ` Alexandre Torgue
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=f6d9e6d7-60ea-85c3-9291-c7c01befc7ef@st.com \
--to=alexandre.torgue@st.com \
--cc=grandmaster@al2klimov.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux@armlinux.org.uk \
--cc=mcoquelin.stm32@gmail.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.