Using conntrack on a 1MC system will waste even more kernel memory!
636 karma · joined May 12, 2011
Using conntrack on a 1MC system will waste even more kernel memory!
There is no need to crack the password. You (as non-root user) can just reset the currently logged in user's password by calling:
dscl localhost -passwd /Search/Users/bob
Please vote: http://vote.aerofs.com/forums/67721-feature-requests/suggest...
Have you ever called a system call by hand using assembly?
Have you ever looked at glibc's source?
Habe you ever looked at the kernel's close() syscall?
But the kernel does not call strlen() on the user-supplied string...
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.
is a absolute no-go. It's a nice and funny kernel module but it dooms the kernel's security.
2. Using FUSE you would have to guaranty that your fs overlaps all other mounted filesystems.
Anyone who's using open() can kill the kernel after loading this module.
This is a very bad idea as path is user-supplied and has to be treated as malicious. An attacker can omit the string-terminator...
As one of the users@kernel.org members I can tell you that the kernel.org admins are very competent.
made my day. :-)
http://knoppix.mirrors.tds.net/pub/linux/frugalware/frugalwa...