Jan Stary <[email protected]> wrote:

> On Oct 17 11:02:19, [email protected] wrote:
> > Jan Stary <[email protected]> wrote:
> > 
> > > Currently, the decription of sndiod -a says
> > > 
> > >   If the flag is off, then it's automatically closed,
> > >   allowing other programs to have direct access to the audio device,
> > >   or the device to be disconnected. The default is off.
> > > 
> > > That's not true anymore: programs only access the audio HW
> > > through the running sndiod, right?
> > 
> > and if there is no running sndiod, then someone who has written a
> > program to access the audio hardware directly, can.
> 
> crw-rw----  1 root  _sndiop   42,   0 Oct 17 19:04 /dev/audio0
> crw-rw----  1 root  _sndiop   42,   1 Oct 16 09:29 /dev/audio1
> crw-rw----  1 root  _sndiop   42,   2 Oct 15 21:24 /dev/audio2
> crw-rw----  1 root  _sndiop   42,   3 Oct 15 21:24 /dev/audio3
> crw-rw----  1 root  _sndiop   42, 192 Oct 15 21:24 /dev/audioctl0
> crw-rw----  1 root  _sndiop   42, 193 Oct 15 21:24 /dev/audioctl1
> crw-rw----  1 root  _sndiop   42, 194 Oct 15 21:24 /dev/audioctl2
> crw-rw----  1 root  _sndiop   42, 195 Oct 15 21:24 /dev/audioctl3
> 
> The device is chgrp'ed precisely so that they _can't_, right?

What if the other program is run as root, and the reader has permission?

Reply via email to