Re: documentation on permissions for cdrom device -- where?
- To: Debian Developers <email@example.com>
- Subject: Re: documentation on permissions for cdrom device -- where?
- From: Kalle Olavi Niemitalo <firstname.lastname@example.org>
- Date: 01 Jan 1999 12:01:52 +0200
- Message-id: <877lv7l3an.fsf@PC486.Niemitalo.LAN>
- In-reply-to: Wichert Akkerman's message of Fri, 1 Jan 1999 04:41:43 +0100
- References: <E0zvMzu-0005Yzemail@example.com> <19981230114111.G1104@efis.ucr.ac.cr> <87yannanxg.fsf@PC486.Niemitalo.LAN> <19990101044143.A2331@cs.leidenuniv.nl>
Wichert Akkerman <firstname.lastname@example.org> writes:
> Previously Kalle Olavi Niemitalo wrote:
> > This solution isn't very good either, since the user can create a
> > setgid program when she's at the console and run it later. Or she can
> > leave a shell running in screen(1). Or just leave a process holding
> > the device open.
> The obvious solution to that is the revoke() system call, which should
> be used by anything that does things like spawning a login-shell and
> giving away groups. It should be in the 2.1 kernels.
Okay, so that prevents her from just keeping the device open. But how
about the two other ways, which rely on preserving the group id and
using it to open the device later?
You could mount all user-writable directories -o nosuid and kill all
user processes after she logs out, but that would seem rather fascist
Or did you mean to junk the groups and instead chown the
audio/scanner/whatever to the console user, like the tty devices are
chowned to their respective users?