Hi,
Can anyone enlighten me or sent me some pointers on the following
problems:
- if I gdb a core of an setuid program, will the code
executed also be setuid?
- if I execute a program, will the memory in which the executable code is
stored read/writable? (i.e. can I insert my own jumps?) I suspect setuid
programs are read-only in memory?
(ps. non-root users)
Another thing (2.2.10 related):
- if I run a stupid malloc-ing and forking for-loop (as a non-privileged
user) every process I try to execute dumps core; is this exploitable?
Furthermore, with this little proggie anyone can "freeze" my system;
i.e. it doesn't halt, but all my resources are eaten up (I can't even
run kill being root) -- can I use another way besides PAM, running top
from inittab or the Sysctl hack to solve this gently (maybe using some
root/kernel memory or perhaps a way to `talk' to init directly??)
I hope this is not too much off-topic and I appreciate any answers,
xander van wiggen
-
Linux SMP list: FIRST see FAQ at http://www.irisa.fr/prive/mentre/smp-faq/
To Unsubscribe: send "unsubscribe linux-smp" to [EMAIL PROTECTED]
