From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com> To: "Alexander A. Klimov" <grandmaster@al2klimov.de> Cc: zohar@linux.ibm.com, dhowells@redhat.com, linux-integrity@vger.kernel.org, keyrings@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] encrypted-keys: Replace HTTP links with HTTPS ones Date: Thu, 23 Jul 2020 02:01:14 +0000 [thread overview] Message-ID: <20200723020114.GG45081@linux.intel.com> (raw) In-Reply-To: <20200716195227.65839-1-grandmaster@al2klimov.de> On Thu, Jul 16, 2020 at 09:52:27PM +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. A commit message should describe action e.g. "Replace HTTP URL with HTTPS URL given the security concerns and the slow deprecation of HTTP." > 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. Please remove this. We don't care about it. Git log should only contain information either for studying or maintaining the kernel source code. > > Signed-off-by: Alexander A. Klimov <grandmaster@al2klimov.de> /Jarkko
WARNING: multiple messages have this Message-ID (diff)
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com> To: "Alexander A. Klimov" <grandmaster@al2klimov.de> Cc: zohar@linux.ibm.com, dhowells@redhat.com, linux-integrity@vger.kernel.org, keyrings@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] encrypted-keys: Replace HTTP links with HTTPS ones Date: Thu, 23 Jul 2020 05:01:14 +0300 [thread overview] Message-ID: <20200723020114.GG45081@linux.intel.com> (raw) In-Reply-To: <20200716195227.65839-1-grandmaster@al2klimov.de> On Thu, Jul 16, 2020 at 09:52:27PM +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. A commit message should describe action e.g. "Replace HTTP URL with HTTPS URL given the security concerns and the slow deprecation of HTTP." > 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. Please remove this. We don't care about it. Git log should only contain information either for studying or maintaining the kernel source code. > > Signed-off-by: Alexander A. Klimov <grandmaster@al2klimov.de> /Jarkko
next prev parent reply other threads:[~2020-07-23 2:01 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-16 19:52 [PATCH] encrypted-keys: Replace HTTP links with HTTPS ones Alexander A. Klimov 2020-07-16 19:52 ` Alexander A. Klimov 2020-07-23 2:01 ` Jarkko Sakkinen [this message] 2020-07-23 2:01 ` Jarkko Sakkinen 2020-07-23 18:53 ` [PATCH v2] " Alexander A. Klimov 2020-07-23 18:53 ` Alexander A. Klimov 2020-07-23 7:45 ` [PATCH] " David Howells 2020-07-23 7:45 ` David Howells
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=20200723020114.GG45081@linux.intel.com \ --to=jarkko.sakkinen@linux.intel.com \ --cc=dhowells@redhat.com \ --cc=grandmaster@al2klimov.de \ --cc=keyrings@vger.kernel.org \ --cc=linux-integrity@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --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: linkBe 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.