errr..?

2000-09-11 Thread Scott Smith
what's up with this? done on a coda volume.. ensomnia:tmp {15} id uid=1000(scott) gid=100(users) groups=100(users), 0(wheel) ensomnia:tmp {16} gcc thing.c ensomnia:tmp {17} ls -l a.out -rwxr-xr-x 1 scott nobody 3512 Sep 11 11:48 a.out* ensomnia:tmp {18} chown root a.out ensomnia:tmp {19} chmod

Re: errr..?

2000-09-11 Thread Jan Harkes
On Mon, Sep 11, 2000 at 01:54:08PM -0700, Scott Smith wrote: > what's up with this? done on a coda volume.. Yes, setuid is bad, it was introduced at some point only because of experimentation with `netbooting' Coda, i.e. running a whole system chrooted into /coda as soon as possible. > ensomnia:

Re: errr..?

2000-09-11 Thread Scott Smith
> > This is AFAIK only possible because you are a member of the > System:Administrators group, which is the Coda equivalent of `root'. A hmmm, I just took myself out of System:Administrators (via pdbtool), did cunlog, kclog, and tried again...I was able to still chown root and chmod u+s my binar

nitpicking

2000-09-11 Thread Robert Forsman
Jan Harkes <[EMAIL PROTECTED]> ,in message <[EMAIL PROTECTED]> , wrote: > And /bin/setuid-wrapper could be something like, > > #!/bin/sh > bin = "$0.real" > if [ -x "$bin" ]; > sudo "$bin" $* > fi I would write that sudo as sudo "$bin" "$@" in order to preve