From: "Michal Suchánek" <msuchanek@suse.de>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc: Peter Huewe <peterhuewe@gmx.de>,
Matthew Garrett <mjg59@google.com>,
linux-integrity <linux-integrity@vger.kernel.org>,
Kari Hiitola <kari@varaani.com>,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org,
Alexander Steffen <Alexander.Steffen@infineon.com>
Subject: Re: Fixing CVE-2017-15361
Date: Thu, 26 Oct 2017 16:57:48 +0200 [thread overview]
Message-ID: <20171026165748.265e6dcf@kitsune.suse.cz> (raw)
In-Reply-To: <20171026140602.syifqbrgysvq7ciy@linux.intel.com>
On Thu, 26 Oct 2017 16:06:02 +0200
Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com> wrote:
> On Thu, Oct 26, 2017 at 02:59:02PM +0200, Michal Suchánek wrote:
> > It does not really matter. People ignore the messages unless looking
> > for something specific as you already noticed. Warn seems adequate
> > because the cipher is weaker than expected but not known to
> > be compromised. People who care can look up the message. People who
> > don't care will ignore it even if it's crit.
>
> Is it worth of trouble to do any driver changes then (open question to
> everyone)? I'm not sure it is worth of trouble to add cruft to the
> driver code for a warning that will likely be ignored anyway.
If the kernel can reliably detect the affected TPMs it saves the
user the work of figuring out where the firmware revision is accessible
on the running machine and what firmware revisions are affected.
Thanks
Michal
next prev parent reply other threads:[~2017-10-26 14:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-25 13:44 Fixing CVE-2017-15361 Jarkko Sakkinen
2017-10-25 14:17 ` Matthew Garrett
2017-10-25 18:53 ` Jarkko Sakkinen
2017-10-25 20:22 ` Jerry Snitselaar
2017-10-26 11:01 ` Jarkko Sakkinen
2017-10-25 22:26 ` Peter Huewe
2017-10-26 11:16 ` Jarkko Sakkinen
2017-10-26 11:27 ` Jarkko Sakkinen
2017-10-26 12:59 ` Michal Suchánek
2017-10-26 14:06 ` Jarkko Sakkinen
2017-10-26 14:57 ` Michal Suchánek [this message]
2017-10-26 17:02 ` Jarkko Sakkinen
2017-10-26 17:03 ` Jarkko Sakkinen
2017-10-26 15:46 ` Alexander.Steffen
2017-10-26 17:08 ` Jarkko Sakkinen
2017-10-26 15:42 ` Alexander.Steffen
2017-10-26 17:00 ` Jarkko Sakkinen
2017-10-26 15:51 ` Alexander.Steffen
2017-10-26 19:07 ` Jarkko Sakkinen
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=20171026165748.265e6dcf@kitsune.suse.cz \
--to=msuchanek@suse.de \
--cc=Alexander.Steffen@infineon.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=kari@varaani.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mjg59@google.com \
--cc=peterhuewe@gmx.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