grip and cdparanoia, must run suid?

2000-05-03 Thread Kenneth Scharf
I installed grip, but I can't run in unless I am root
(sudo, or suid).  The error I get is 'can't access cd
rom drive'.  My /dev/scd1 is owned by root, group is
cdrom.  The drive is actually on /dev/hdc physically
but I am running scsi-ide emulation.  I also have a
'real' scsi cdrom that is /dev/scd0.  I added myself
to the cdrom group (edited /etc/group as root) and
logged out and back in as myself.  No joy, still can't
run grip or cdparanoia (actually it was cdparanoia
that issued the error message).  I did chmod +s on
cdparanoia and grip and then it worked.  But I should
be able to access the cdrom if I'm in the cdrom group?
 I can access my /dev/dsp device by adding myself to
the audio group (I don't think xmmm is suid, I can run
it as a user in the audio group).
Ideas?


=
Amateur Radio, when all else fails!

http://www.qsl.net/wa2mze

Debian Gnu Linux, Live Free or .



__
Do You Yahoo!?
Send instant messages  get email alerts with Yahoo! Messenger.
http://im.yahoo.com/


Re: grip and cdparanoia, must run suid?

2000-05-03 Thread Lee Bradshaw
On Wed, May 03, 2000 at 05:37:42AM -0700, Kenneth Scharf wrote:
 I installed grip, but I can't run in unless I am root
 (sudo, or suid).  The error I get is 'can't access cd
 rom drive'.  My /dev/scd1 is owned by root, group is
 cdrom.  The drive is actually on /dev/hdc physically
 but I am running scsi-ide emulation.  I also have a
 'real' scsi cdrom that is /dev/scd0.  I added myself
 to the cdrom group (edited /etc/group as root) and
 logged out and back in as myself.  No joy, still can't
 run grip or cdparanoia (actually it was cdparanoia
 that issued the error message).  I did chmod +s on
 cdparanoia and grip and then it worked.  But I should
 be able to access the cdrom if I'm in the cdrom group?
  I can access my /dev/dsp device by adding myself to
 the audio group (I don't think xmmm is suid, I can run
 it as a user in the audio group).
 Ideas?

If it's anything like real scsi devices, then the scsi generic
devices must be writeable. Unfortunately these device id's can change
if you add or remove scsi devices. I wrote a script to correct the
permissions at system startup, but I must not be using it since I
can't find the script.

Anyway, notice that sg2 and sg3 are writeable by group cdrom. Only
one of the devices is really writeable, but the script changes all sg
devices back to crw--- root:root and then all cdroms (writeable or
not) to crw-rw root:cdrom.

freefall ~/technical $ ll /dev/sg*
crw---1 root root  21,   0 Aug 18  1999 /dev/sg0
crw---1 root root  21,   1 Aug 18  1999 /dev/sg1
crw---1 root root  21,  10 Aug 18  1999 /dev/sg10
crw---1 root root  21,  11 Aug 18  1999 /dev/sg11
crw---1 root root  21,  12 Aug 18  1999 /dev/sg12
crw---1 root root  21,  13 Aug 18  1999 /dev/sg13
crw---1 root root  21,  14 Aug 18  1999 /dev/sg14
crw---1 root root  21,  15 Aug 18  1999 /dev/sg15
crw---1 root root  21,  16 Aug 18  1999 /dev/sg16
crw-rw1 root cdrom 21,   2 Aug 18  1999 /dev/sg2
crw-rw1 root cdrom 21,   3 Aug 18  1999 /dev/sg3
crw---1 root root  21,   4 Aug 18  1999 /dev/sg4
crw---1 root root  21,   5 Aug 18  1999 /dev/sg5
crw---1 root root  21,   6 Aug 18  1999 /dev/sg6
crw---1 root root  21,   7 Aug 18  1999 /dev/sg7
crw---1 root root  21,   8 Aug 18  1999 /dev/sg8
crw---1 root root  21,   9 Aug 18  1999 /dev/sg9

I think cdparanoia had some docs on how to determine the scsi generic
device number to go along with a particular device, but I don't know how
ide emulation affects it.

-- 
Lee Bradshaw [EMAIL PROTECTED] (preferred)
Alantro Communications   [EMAIL PROTECTED]