Thread (19 messages) 19 messages, 6 authors, 2017-10-26

Fixing CVE-2017-15361

From: Michal Suchánek <hidden>
Date: 2017-10-26 14:57:54
Also in: linux-integrity, lkml

On Thu, 26 Oct 2017 16:06:02 +0200
Jarkko Sakkinen [off-list ref] wrote:
On Thu, Oct 26, 2017 at 02:59:02PM +0200, Michal Such?nek wrote:
quoted
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
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help