On Wed, Sep 19, 2007 at 11:12:33PM +0100, Stuart Henderson wrote:I agree, except that there's the warning that you don't put anyone in sudo that you wouldn't trust with root access. Lets take a typical family setup. Mom is the SA who knows the root password. Dad can be operator and do stuff with sudo. However, the kids may just want to listen to CDs, watch DVDs, access their homework on a USB stick, rip a CD to MP3 and transfer it to their player or move MP3s from their player and burn them to a CD. Is it appropriate for the kids to use sudo or is there a security risk since you do not want the kids to get root. They may also need to have the modem access the internet. I don't know the details of this on OBSD yet since I use dialup via my Debian box. Just not e.g. hard drives. However, suppose you want to mount a USB/CD, check something, unmount it, and mount another? I don't see a way to tell amd to unmount before it timesout. ---- Your suggest is similar to the way devices are handled in Debian. On my Debian box, I'm in the following groups for the following reasons: dtutty: standard default login group adm: so I can read logs dialout: so I can use minicom to access the modem directly cdrom: so I can mount the cdrom, burn CDs, etc floppy: ditto for floppies audio: so I can adjust the mixer settings and hear music and movies dip: so I can pon the internet video: so I can watch movies plugdev: so I can mount and access USB sticks, Palm, etc staff: similar to OBSD's operator group. ssh: So I can limit who can run ssh. The definitive info on groups in Debian comes from the documentation with the base-passwd package in the users-and-groups.html file which I can email to you if you like: 19 KB in html, 5.3 KB in text. The document itself is under the GPLv2 but you will only be reading it not modifying it to include in OBSD :)) ------ If it weren't for the warnings about sudo and people you don't trust with root, I think that using sudo with groups is the best approach. Then you don't have to change bits of the system all over the place. It _may_ (I don't know) be easier or better to close any security concerns in the commands that would be run under sudo (such as mount). Then there could just be provided a default sudoers file that gave abilities to groups, with no default members in those groups. Just my random thoughts. I'm very new to OBSD and have been using Debian since before it trended towards clicky-pointy Lindows. :) Doug.
| Alan Cox | [PATCH 01/76] drivers/serial/crisv10.c: add missing put_tty_driver |
| Greg Kroah-Hartman | [PATCH 004/196] Chinese: add translation of SubmittingPatches |
| James Bottomley | Re: Integration of SCST in the mainstream Linux kernel |
| Ingo Molnar | [bug] mm/slab.c boot crash in -git, "kernel BUG at mm/slab.c:2103!" |
git: | |
| Jon Smirl | Re: VCS comparison table |
| Junio C Hamano | [RFD] On deprecating "git-foo" for builtins |
| Jakub Narebski | Re: [RFC] Git User's Survey 2008 |
| Eric Wong | [PATCH] archimport improvements |
| Richard Stallman | Real men don't attack straw men |
| GVG GVG | ssh_exchange_identification: Connection closed by remote host |
| David H. Lynch Jr. | Re: That whole "Linux stealing our code" thing |
| Marcos Laufer | dmesg IBM x3650 OpenBSD 4.3 |
| Jeff Garzik | Re: [bug?] tg3: Failed to load firmware "tigon/tg3_tso.bin" |
| David Miller | [GIT]: Networking |
| Mark Lord | Re: 2.6.25-rc8: FTP transfer errors |
| David Miller | Re: [BUG] New Kernel Bugs |
