l i n u x - u s e r s - g r o u p - o f - d a v i s
L U G O D
 
Next Meeting:
December 2: Social gathering
Next Installfest:
TBD
Latest News:
Nov. 18: Club officer elections
Page last updated:
2002 Jun 30 16:52

The following is an archive of a post made to our 'vox-tech mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
Re: [vox-tech] Sound Trouble with trident module
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vox-tech] Sound Trouble with trident module



On Sun, 30 Jun 2002, David Margolis wrote:
> I've read that this isn't the most secure way to do this, but I don't know
> why sound would necessarly be a security issue (anyone out there pipe in
> if you have an opinion on this)...
> 
> chmod 666 /dev/dsp*
> chmod 666 /dev/audio*
> chmod 666 /dev/mixer*

Side info: One item of security for not doing this is on multi-user
systems; users can sample from the audio devices and record from a
microphone if attached. They can also play audio when remote. Even though
use of the audio group is the preferred/suggested method, I have known
single user systems that were configured in the way you mention above.

> also, for convenience of playing audio cds
> chmod 666 /dev/cdrom* (this one is probably a bad idea if you ever intend
> to have priate files on a cdrom).

Side info:
CDROM could be 444 unless you have RW capabilities. Also, often /dev/cdrom
is set as a symlink to point to your read device. The default for chmod
when applied to symlinks is to apply them to where they are pointing, not
the symlink. They should just be aware of the permissions set to the
device if it ever changed to a fixed disk or zip drive or...

> The other method for dealing with giving sound to users was only
> slightly more involved and I believe it had to do with creating a
> group that had ownership to
> these devices and adding appropriate users to this group.

Many distros come with an Audio group. You can just add yourself to it
along with anyone that should be able to read/write to the audio
devices. Be careful not to go group-happy and add yourself to too many
places; there are (were - things may have changed) static limits to how
many groups a user can belong. 32? 64? Dont recall. It is in the code.

> Dave
> 
> On Sun, 30 Jun 2002, Rusty Minden wrote:
> 
> > I have compiled the trident module and as root it works sound is
> > fine, but as a user it will not work. It has to be a permission
> > thing or perhaps a group membership, but I am not sure.
> >
> > ALi Sound Card (tridentt.o module)
> > I noticed that the /dev/aidio has owner root and group audio should I add
> > myself to the group?
> >
> > Rusty

_______________________________________________
vox-tech mailing list
vox-tech@lists.lugod.org
http://lists.lugod.org/mailman/listinfo/vox-tech



LinkedIn
LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
facebook
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
O'Reilly and Associates
For numerous book donations.