On Fri, Aug 12, 2005 at 05:43:16AM -0700, Grant wrote
> Actually it looks like rebooting after adding the user to the audio
> group has fixed this. Does that make sense?
It's actually PAM that's screwing things up. There are two long-term
solutions...
1) remove PAM altogether, which I eventually did, and am very happy
with. Note, you have to be careful.
2) comment out all the entries in the specific PAM config file that
sets permissions for devices. My main machine totally died on me
last night, so I have to check the Gentoo archive on the web. I
think the file you want to modify is /etc/security/console.perms
by commenting out the line...
<console> 0660 <sound> 0660 root.audio
Thanks to other problems, I eventually commented out the entire file.
A few more problems, and I dumped PAM entirely. IMHO, PAM belongs in
the optional hardened security configs, along with NSA Selinux, etc. If
you're an ISP offering shell access to several thousand customers, PAM
makes sense. However, it is *NOT* necessary for the average desktop,
and only gets in the way.
--
Walter Dnes <[EMAIL PROTECTED]>
My musings on technology and security at http://tech_sec.blog.ca
--
[email protected] mailing list
