echo "engage killswitch_engage -1" \
> /sys/kernel/security/killswitch/control
I’m not a kernel dev, but I didn’t see any obvious attempt in the code to detect such an attempt.
Posted May 8, 2026 14:57 UTC (Fri) by sashal (✭ supporter ✭, #81842) [Link] (8 responses)
Posted May 8, 2026 15:11 UTC (Fri) by mb (subscriber, #50428) [Link] (6 responses)
Posted May 8, 2026 15:36 UTC (Fri) by sashal (✭ supporter ✭, #81842) [Link] (5 responses)
Adding in lockdown support like Jon suggested would address this concern?
Posted May 8, 2026 15:46 UTC (Fri) by mb (subscriber, #50428) [Link] (4 responses)
Posted May 8, 2026 16:11 UTC (Fri) by sashal (✭ supporter ✭, #81842) [Link] (3 responses)
Posted May 8, 2026 16:53 UTC (Fri) by mb (subscriber, #50428) [Link] (2 responses)
Posted May 8, 2026 17:00 UTC (Fri) by sashal (✭ supporter ✭, #81842) [Link]
This sounds like you've listed another usecase for killswitch: use it to remove all the functionality you don't want, followed by killswitching ks_attr_open (or something like that) to disable killswitch itself :)
Posted May 9, 2026 6:21 UTC (Sat) by pabs (subscriber, #43278) [Link]
livepatch is very useful on a desktop, I don't want to have to reboot for security updates their either.
Posted May 8, 2026 19:29 UTC (Fri) by songmaster (subscriber, #1748) [Link]
If a cracker already has a permanent route to root installed in a Linux system and their vulnerability has just been discovered, they might killswitch the killswitch like this to prevent the sysadmins from disabling that entrance-route until they can find/install another way in.
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。