This is a discussion on "Safe" permissions on /dev/sg0? within the Slackware Linux Support forums, part of the Unix Operating Systems category; --> Hi: I'm a bit of a newbie to Slackware (and to Linux, for that matter.) I've done my research ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hi: I'm a bit of a newbie to Slackware (and to Linux, for that matter.) I've done my research and have managed to get my ATAPI CD-RW drive working under nautilus-cd-burner. The only problem that I have is that I must be logged in as root to actually write to the device. I know that if I were to change the permissions on /dev/sg0 (this is the /dev entry my CD-RW uses), I would be able to write to the CD-RW drive without having to be logged on as root. I ran across a very similar post while Googling in the Debian mailing list that suggested changing the permissions, but I wanted some other opinions before I did that. My question is to whether or not changing the permissions would be a security risk. As it stands, the default permission for /dev/sg0 are: crw------- 1 root root 21, 0 1999-04-12 23:24 /dev/sg0 If I were to change group ownership to cdrom and give rw privileges to the group, would that be a horrible security risk? Thanks, Mike |
| |||
| Mike N. <postmaster@localhost> wrote: >crw------- 1 root root 21, 0 1999-04-12 23:24 /dev/sg0 > >If I were to change group ownership to cdrom and give rw privileges to >the group, would that be a horrible security risk? No, but I guess you would like to use /dev/sr0 instead for your burning needs. (And it already has the correct group and access bits.) |
| ||||
| Petri Kaukasoina wrote: > No, but I guess you would like to use /dev/sr0 instead for your burning > needs. (And it already has the correct group and access bits.) Thank you, Petri. I had originally modified my fstab to mount /dev/sr0 as my burner, but for some reason I still require rw privileges on /dev/sg0 to allow myself to use nautilus-cd-burner. I say "some reason". The actual error message was along the lines of not being able to open the SCSI driver on /dev/sg0. Once I changed the permissions as I'd stated in my original post, everything is working fine. Thanks again, Mike |