From: "Alexander A. Klimov" <grandmaster@al2klimov.de> To: zohar@linux.ibm.com, dhowells@redhat.com, jarkko.sakkinen@linux.intel.com, linux-integrity@vger.kernel.org, keyrings@vger.kernel.org, linux-kernel@vger.kernel.org Cc: "Alexander A. Klimov" <grandmaster@al2klimov.de> Subject: [PATCH v2] encrypted-keys: Replace HTTP links with HTTPS ones Date: Thu, 23 Jul 2020 18:53:15 +0000 [thread overview] Message-ID: <20200723185315.71039-1-grandmaster@al2klimov.de> (raw) In-Reply-To: <20200723020114.GG45081@linux.intel.com> Rationale: Reduces attack surface on kernel devs opening the links for MITM as HTTPS traffic is much harder to manipulate. Signed-off-by: Alexander A. Klimov <grandmaster@al2klimov.de> --- v2: Shortened commit message. Oh, and it wasn't my intention to address the slow deprecation of plain HTTP. include/keys/encrypted-type.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/keys/encrypted-type.h b/include/keys/encrypted-type.h index 38afb341c3f2..abfcbe02001a 100644 --- a/include/keys/encrypted-type.h +++ b/include/keys/encrypted-type.h @@ -2,7 +2,7 @@ /* * Copyright (C) 2010 IBM Corporation * Copyright (C) 2010 Politecnico di Torino, Italy - * TORSEC group -- http://security.polito.it + * TORSEC group -- https://security.polito.it * * Authors: * Mimi Zohar <zohar@us.ibm.com> -- 2.27.0
WARNING: multiple messages have this Message-ID (diff)
From: "Alexander A. Klimov" <grandmaster@al2klimov.de> To: zohar@linux.ibm.com, dhowells@redhat.com, jarkko.sakkinen@linux.intel.com, linux-integrity@vger.kernel.org, keyrings@vger.kernel.org, linux-kernel@vger.kernel.org Cc: "Alexander A. Klimov" <grandmaster@al2klimov.de> Subject: [PATCH v2] encrypted-keys: Replace HTTP links with HTTPS ones Date: Thu, 23 Jul 2020 20:53:15 +0200 [thread overview] Message-ID: <20200723185315.71039-1-grandmaster@al2klimov.de> (raw) In-Reply-To: <20200723020114.GG45081@linux.intel.com> Rationale: Reduces attack surface on kernel devs opening the links for MITM as HTTPS traffic is much harder to manipulate. Signed-off-by: Alexander A. Klimov <grandmaster@al2klimov.de> --- v2: Shortened commit message. Oh, and it wasn't my intention to address the slow deprecation of plain HTTP. include/keys/encrypted-type.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/keys/encrypted-type.h b/include/keys/encrypted-type.h index 38afb341c3f2..abfcbe02001a 100644 --- a/include/keys/encrypted-type.h +++ b/include/keys/encrypted-type.h @@ -2,7 +2,7 @@ /* * Copyright (C) 2010 IBM Corporation * Copyright (C) 2010 Politecnico di Torino, Italy - * TORSEC group -- http://security.polito.it + * TORSEC group -- https://security.polito.it * * Authors: * Mimi Zohar <zohar@us.ibm.com> -- 2.27.0
next prev parent reply other threads:[~2020-07-23 18:53 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 2020-07-23 2:01 ` Jarkko Sakkinen 2020-07-23 18:53 ` Alexander A. Klimov [this message] 2020-07-23 18:53 ` [PATCH v2] " 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=20200723185315.71039-1-grandmaster@al2klimov.de \ --to=grandmaster@al2klimov.de \ --cc=dhowells@redhat.com \ --cc=jarkko.sakkinen@linux.intel.com \ --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.