From: "Bernat, Yehezkel" <yehezkel.bernat@intel.com>
To: "stable@vger.kernel.org" <stable@vger.kernel.org>
Cc: "mika.westerberg@linux.intel.com"
<mika.westerberg@linux.intel.com>,
"andreas.noever@gmail.com" <andreas.noever@gmail.com>,
"Jamet, Michael" <michael.jamet@intel.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"lukas@wunner.de" <lukas@wunner.de>
Subject: [STABLE 4.13] thunderbolt: fixes for key handling
Date: Mon, 11 Sep 2017 17:19:53 +0000 [thread overview]
Message-ID: <1505150379.4818.84.camel@intel.com> (raw)
Upstream commits to be applied
==============================
8fdd6ab36197 thunderbolt: Remove superfluous check
0956e4116922 thunderbolt: Make key root-only accessible
e545f0d8a54a thunderbolt: Allow clearing the key
The reason why these should be applied
======================================
8fdd6ab36197 - the below patches depend on this one.
0956e4116922 is a security-related fix, it prevents non-root users from
reading the key.
e545f0d8a54a fixes functionality issue where if the key was rejected,
it's impossible to use "connect once" flow to connect without a key
even if the user chose to.
How to apply it
===============
Cherry-picking them to v4.13 passes cleanly.
reply other threads:[~2017-09-11 17:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1505150379.4818.84.camel@intel.com \
--to=yehezkel.bernat@intel.com \
--cc=andreas.noever@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=lukas@wunner.de \
--cc=michael.jamet@intel.com \
--cc=mika.westerberg@linux.intel.com \
--cc=stable@vger.kernel.org \
/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).