You're missing something here. If the attacker can access the file during boot, they already has root privileges on your machine, since they were able to install an initscript...
That said, I agree that taking broken userland behaviour in consideration in this case is stupid; Jaunty is unlikely to ship 2.6.37 anyway. Anyone installing a non-distro kernel should know what they're doing, and thus be able to also patch the relevant package that breaks because of this.
Posted Nov 22, 2010 15:22 UTC (Mon) by Karellen (subscriber, #67644)
[Link]
I am aware of that, and partly agree, but that response falls very close to the "it's only a theoretical problem; there's no way anyone will be able to actually exploit it" argument beloved of some proprietary software companies with terrible security track records.
Bolstered by the old cryptography saw that anyone can invent a cryptosystem which they themselves are not smart enough to crack, I'm not going to claim that just because I can't think of a way to exploit this problem, it cannot be exploited. Attackers can be fiendishly devious. I'd rather err on the side of caution.
Jaunty not even getting security updates.
Posted Nov 23, 2010 5:58 UTC (Tue) by error27 (subscriber, #8346)
[Link]
Kernel hackers upgrade their kernel a lot. You can't even imagine how enraged they would be if your idea was adopted. :P Also we want people to upgrade their kernels as easily as possible because we need testers.
If you're running a distro kernel then changing the permissions on kallsysms is pointless anyway.