Remeber when I ranted about RH 6.0...

[cdoerbec at cso.fmr.com (Christoph Doerbeck A242369)]

Derek Martin wrote:
> On Thu, 29 Jul 1999, Christoph Doerbeck A242369 wrote:
> 
> > It's a scripted feature for X11 logins, not you general console logins (tty
> ).
> > The RedHat way applies to any login that's considered a to be a console
> > including the virtual tty logins.
> > 
> > This might be another good 30 minute topic...
> > 
> 
> I'm not sure what you're trying to say here... but it sounds like you're
> saying that login doesn't change the ownership on any terminal, and that
> only X11 changes the ownership of the console.  I assure you that this is
> not the case.  
> 
> 
>  ...snip...
>

Well, initially I was caught off guard by the new default behaviour of 
the RH 6.0 login.  By logging onto the system via any of the defined
console ttys (console, :0, tty??), the permissions and ownerships of
/dev/audio*, video*, mixer, fd*, etc... would change.

More research has shown a similiar behaviour on SUN systems.  I knew that the
'login' executible changes permissions on the login tty/pts. But, the SUN
implementation of PAM also looks at /etc/logindevperm to change other
/dev-file permissions (/dev/sound, /dev/mouse, /dev/keyboard, etc...)

So, all things being said... I am no longer ranting, and have realised that
a little education was due on my part.

If someone can answer this:  xterm on SUN is not setuid, what changes
the permissions on /devices/pseudo/* when xterm opens a new pseudo device?

- Christoph


-
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at blu.org (Subject line is ignored).