Bug#393661: libpam-devperm: Should give access to /dev/dsp as well

2006-10-30 Thread Peter Mathiasson
On Tue, Oct 17, 2006 at 12:59:16PM +0200, Petter Reinholdtsen wrote:
 I just tested the libpam-devperm package, and it seem to work just
 fine.  But the /dev/dsp device now used for audio is not in the list
 of devices to update, so KDE do not get access to its sound device.  I
 guess it used to be a symlink with devfs, but now it is a real device
 
 I applied this patch to fix it:

I'm quite busy right now, so it would be great if you could upload an
NMU with your changes.

Otherwise I'll see if I can get to it next weekend.

Thanks.




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#393661: libpam-devperm: Should give access to /dev/dsp as well

2006-10-17 Thread Petter Reinholdtsen

Package:  libpam-devperm
Version:  1.5-2
Severity: important
Tags: patch

I just tested the libpam-devperm package, and it seem to work just
fine.  But the /dev/dsp device now used for audio is not in the list
of devices to update, so KDE do not get access to its sound device.  I
guess it used to be a symlink with devfs, but now it is a real device

I applied this patch to fix it:

--- /etc/logindevperm.orig   2006-10-17 10:51:58.0 +
+++ /etc/logindevperm   2006-10-17 10:53:08.0 +
@@ -24,7 +24,7 @@
 :0 0600 /dev/cdrecorder:/dev/cdrecorder1:/dev/cdrecorder2:/dev/cdrecorder3
 :0 0600 /dev/dvd:/dev/dvd1:/dev/dvd2:/dev/dvd3
 :0 0600 /dev/zip:/dev/zip1:/dev/zip2:/dev/zip3
-:0 0600 /dev/dsp0:/dev/dsp1:/dev/dsp2:/dev/dsp3
+:0 0600 /dev/dsp:/dev/dsp0:/dev/dsp1:/dev/dsp2:/dev/dsp3
 :0 0600 /dev/fd0:/dev/fd0u1440:/dev/fd0h1440:/dev/fd0u720:/dev/fd0h720
 :0 0600 /dev/fd1:/dev/fd1u1440:/dev/fd1h1440:/dev/fd1u720:/dev/fd1h720
 :0 0600 /dev/sequencer:/dev/sequencer2:/dev/music

With this patch in place, the device got correct permissions when
logging in as my test user:

  # ls -l /dev/dsp
  crw--- 1 test audio 14, 3 2006-10-16 15:20 /dev/dsp
  #

Please update the package with this fix, to make it usable out of the
box.  The only other change I did to enable it was to edit
/etc/pam.d/common-session, adding pam_devperm to get this content:

  session required pam_unix.so
  session required pam_devperm.so

I did not have to edit /etc/login.defs to enable CLOSE_SESSIONS.  The
README.Debian file claim that this is required, but the file itself
claim that the setting is obsolete, so I left it untouched.  It worked
just fine without enabling CLOSE_SESSIONS, so I guess the
README.Debian content should be changed.

Friendly,
-- 
Petter Reinholdtsen


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]