Not in 4.17 after all

Posted Apr 3, 2018 22:39 UTC (Tue) by corbet (editor, #1)
Parent article: Kernel lockdown in 4.17?

Discussion on the linux-kernel list has made it clear that there is not yet a consensus around the lockdown patches, so security maintainer James Morris has said that he no longer plans to push them for 4.17.

to post comments

Not in 4.17 after all

Posted Apr 4, 2018 2:53 UTC (Wed) by unixbhaskar (guest, #44758) [Link] (2 responses)

For everyone's sake, here is the pointer to the discussion in details...

https://lkml.org/lkml/2018/3/30/602

Not in 4.17 after all

Posted Apr 5, 2018 6:40 UTC (Thu) by ashkulz (guest, #102382) [Link] (1 responses)

Further down the thread, Linus says he is unlikely to merge it at all:

http://lkml.iu.edu/hypermail/linux/kernel/1804.0/01607.html

Not in 4.17 after all

Posted Apr 5, 2018 11:24 UTC (Thu) by smurf (subscriber, #17840) [Link]

Umm, not entirely. The part Linus is objecting to is the idea that auto-enabling the lockdown features when secure-boot is in effect makes any sense whatsoever. Linus' opinion is that whether you boot securely and whether the kernel is subsequently locked down are two independent concepts and it's stupid to conflate them.