From: ebiederm@xmission.com (Eric W. Biederman)
To: Jiri Kosina <jikos@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
security@kernel.org, linux-doc@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Subject: Re: [PATCH] Documentation/admin-guide: Embargoed hardware security issues
Date: Mon, 05 Aug 2019 09:40:21 -0500 [thread overview]
Message-ID: <87blx3n0a2.fsf@xmission.com> (raw)
In-Reply-To: <nycvar.YFH.7.76.1908040214090.5899@cbobk.fhfr.pm> (Jiri Kosina's message of "Sun, 4 Aug 2019 02:17:00 +0200 (CEST)")
I skimmed this and a couple things jumped out at me.
1) PGP and S/MIME because of their use of long term keys do not provide
forward secrecy. Which can makes it worth while to cryptographically
factor a key or to obtain knowledge of a private key without the key
holders knowledge. As the keys will be used again and again over a
long period of time.
More recent protocol's such as Signal's Double Ratchet Protocol
enable forward secrecy for store and foward communications, and
remove the problem of long term keys.
2) The existence of such a process with encrypted communications to
ensure long term confidentiality is going to make our contact people
the targets of people who want access to knolwedge about hardware
bugs like meltdown, before they become public.
I am just mentioning these things in case they are not immediately
obvious to everyone else involved, so that people can be certain
they are comfortable with the tradeoffs being made.
Eric
next prev parent reply other threads:[~2019-08-05 14:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 13:01 [PATCH] Documentation/admin-guide: Embargoed hardware security issues Greg Kroah-Hartman
2019-07-25 21:13 ` Jonathan Corbet
2019-07-26 14:47 ` Thomas Gleixner
2019-08-15 21:20 ` Greg Kroah-Hartman
2019-08-15 22:12 ` Randy Dunlap
2019-08-15 22:31 ` Greg Kroah-Hartman
2019-08-15 23:10 ` Randy Dunlap
2019-08-02 4:49 ` Willy Tarreau
2019-08-02 6:57 ` Greg Kroah-Hartman
2019-08-02 9:24 ` Willy Tarreau
2019-08-04 0:17 ` Jiri Kosina
2019-08-04 0:21 ` Jiri Kosina
2019-08-05 14:40 ` Eric W. Biederman [this message]
2019-08-05 14:59 ` Greg Kroah-Hartman
2019-08-05 15:12 ` Greg Kroah-Hartman
2019-08-15 21:04 ` Greg Kroah-Hartman
2019-08-15 21:25 ` [PATCH v2] " Greg Kroah-Hartman
2019-08-15 22:15 ` Randy Dunlap
2019-08-15 22:31 ` Greg Kroah-Hartman
2019-08-20 14:58 ` Josh Poimboeuf
2019-08-20 16:58 ` Greg Kroah-Hartman
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=87blx3n0a2.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=jikos@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=security@kernel.org \
--cc=tglx@linutronix.de \
/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).