@MattE.Эллен that seems UNIXy enough to me to try on U&L

@terdon (re. /proc/sys/fs/protected_*) well the kernel does all the other access controls too, and doing that in the kernel makes it immediately available to all tools. More to the point, the kernel is the only place where those checks can be done without races. The vulnerability being thwarted there is something like putting a symlink in /tmp, and then tricking a privileged process into following it (modifying /etc/passwd or whatever).

If the privileged process tries to check it first, the attacker can still race to change an allowed file to a symlink, and they might get to try again and again until it works. (Sorry if I'm repeating what you already know, I just noticed the linked article didn't seem to explain it too much.)

Mods - Looking for guidance on how you'd like to handle the protest statements I find here. I'm flagging them. Do you want me to edit them out when found or leave that to you?

@NotTheDr01ds at this point, I think a flag would be good, just in case The System doesn't also alert us. In this situation, rollback wars seem likely, and we just don't need that noise.

@JeffSchaller Agreed, and yeah, I'd never rollback a second time, but I'm completely good with you handling it end-to-end ;-)