hallo, so much for file permissions, but: alexm@quake:/ > id uid=1000(alexm) gid=100(users) groups=100(users) alexm@quake:/ > ls -l sh -rwsr-xr-x 1 root root 387764 Jun 28 00:27 sh* alexm@quake:/ > ./sh alexm@quake:/ > id uid=1000(alexm) gid=100(users) groups=100(users) :-o wasn't i supposed to get euid of root? or does suse's /bin/sh do some checks i am not aware of? thanks, -alexm P.S. btw, just checked it with /usr/bin/ksh and it does give the euid 0.
On Wed, 28 Jun 2000, alex medvedev wrote:
hallo,
so much for file permissions, but:
alexm@quake:/ > id uid=1000(alexm) gid=100(users) groups=100(users) alexm@quake:/ > ls -l sh -rwsr-xr-x 1 root root 387764 Jun 28 00:27 sh* alexm@quake:/ > ./sh alexm@quake:/ > id uid=1000(alexm) gid=100(users) groups=100(users)
:-o
wasn't i supposed to get euid of root? or does suse's /bin/sh do some checks i am not aware of?
AFAIK bash and *csh drop euid. Bye, Thomas -- Thomas Biege, SuSE GmbH, Schanzaeckerstr. 10, 90443 Nuernberg E@mail: thomas@suse.de Function: Security Support & Auditing "lynx -source http://www.suse.de/~thomas/thomas.pgp | pgp -fka" Key fingerprint = 09 48 F2 FD 81 F7 E7 98 6D C7 36 F1 96 6A 12 47
participants (2)
-
alex medvedev -
Thomas Biege