News for hackers. Stuff that matters.
Re:Kernel module for advanced rickrolling replaces open() call by muppetman on Thursday September 08, 2011 @03:51AM (#2973015)
You're inserting a dodgy bit of a code into a live running kernel. You are an attacker! I mean, valid technicality, but really? If you've got the ability to insert any module you want, you have the ability (ok, not always, but usually) to rm -rf /
Re:Kernel module for advanced rickrolling replaces open() call by KonradKlause on Thursday September 08, 2011 @03:53AM (#2973023)
Bullshit.

Anyone who's using open() can kill the kernel after loading this module.

Re:Kernel module for advanced rickrolling replaces open() call by dexen on Thursday September 08, 2011 @04:22AM (#2973094)
I guess you meant, ``Anyone who's using open() can kill the kernel after somebody else loads the module.''. Which is far worse: any unprivileged user, say the victim of rickroll, can bite back hard.
Re:Kernel module for advanced rickrolling replaces open() call by gfodor on Thursday September 08, 2011 @05:53AM (#2973236)
This seems like a feature not a bug.
Re:Kernel module for advanced rickrolling replaces open() call by burgerbrain on Thursday September 08, 2011 @03:55AM (#2973027)
Probably best that any user can kill the kernel in this situation, if you stop to think about it.
Re:Kernel module for advanced rickrolling replaces open() call by muppetman on Thursday September 08, 2011 @04:14AM (#2973077)
Anyone who can load a kernel module can do _whatever they want_. That was my point, which you've obviously missed.
Re:Kernel module for advanced rickrolling replaces open() call by KonradKlause on Thursday September 08, 2011 @04:16AM (#2973082)
And you are obviously missing that modern operating systems have more than just one user. :-)
Re:Kernel module for advanced rickrolling replaces open() call by muppetman on Thursday September 08, 2011 @04:26AM (#2973104)
I'm genuinely interested - what do you mean? It's my understanding (and please, correct me if I'm wrong) that if you're able to insmod a non-standard kernel module into a linux system, you are root already. I don't understand what this has to do with unix being multi-user, only root has the ability to insmod /tmp/haha.ko Please note I'm not talking about the ability of the kernel to automatically load modules as required. That's only from the /lib/modules path and you need to be root have to inserted a module in there anyway.

And if you have that ability, worrying about the security of a module such as this seems, to me, totally and utterly pointless, because you could be inserting a rootkit, or a module that randomly deletes a file every time you press the letter A etc.

So could you explain what you mean please? Why be concerned about security when security is already compromised? How does it being multi-user make a difference?

Re:Kernel module for advanced rickrolling replaces open() call by KonradKlause on Thursday September 08, 2011 @04:31AM (#2973113)
Sure.

Suppose your admin is a funny guy and loads this kernel module at April 1st. I (Jonny non-root user) can no longer listen to my favorite mp3, because the kernel module changes the path all the time. The admin loughs and has fun.

But then later I call open() with some fancy arguments and take over the whole machine (or at least crash it). This is the part where I lough.

Re:Kernel module for advanced rickrolling replaces open() call by muppetman on Thursday September 08, 2011 @04:49AM (#2973142)
Ahhh right, yes, Ok, I see what you mean. If you loaded this on a serious system, you're insane. But right, I see your point.