"Dr. Michael Weller" wrote:
> > I was always under the impression that it needed this to change the
> > permissions on the /dev/ttyp* that it was using. Usually login does it
> > for you when you login, but you don't login to an xterm. I've removed it
> > before with out any problems.
> Ah yes, I admit I forgot this. It shouldn't be too much of a problem
> for basic operation but some application might want to open/modify the
> actual terminal device. An example is mesg -y or -n which en/disables
> screen messages by write, talkd and others.
> Another thing is the utmp entry for who. You must run as root too to
> modify it.
Mmmm ... ok, it's sounds reasonable. We must assume that the system
where we are loggin in is a "secure" system, owned by root. When you log
in the root must do some duty to give you a "personal" environment, so
your processes, your devices, and so on. It's correct that usually this
job is done by login, but I must say that login, a root-suid program, do
the job, throws your shell, and kill himself. No setuid processes left.
I'm thinking if it's possible for the xterm to use a setuid wrapper to
launch the application (shell or whatever), so the xterm doesn't need to
be setuid.
--
Kanna (Lorenzo Canovi) [EMAIL PROTECTED]
---------------------------------------------------------------
^ ^ L.U.P.O. (Linux User Perennemente Occupato)
''___O Member of PLUTO (http://www.pluto.linux.it/)
_____) Homepage: http://www.lapam.mo.it/home/kanna/
