On Mon, 2004-11-22 at 22:21 -0500, Sean Middleditch wrote: > One possible (worst case scenario) problem with > having all those apps have access is if a bug is present in the kernel- > level sound system, local users could exploit it, I don't think hypothetical kernel flaws should dictate GNOME's sound architecture. If the Linux kernel has a bug, clearly, it should be fixed. Introducing a large chunk of newly-written code which listens on a network socket sounds much more likely attack vector. > while with a sound > server controlled by SELinux (Sickeningly Elaborate Linux?) or some > similar mechanism guarantees that users can't run malicious code that > accesses the device files. Actually, SELinux can restrict access to SHM segments (the "shm" security class), in addition to the sound device itself. So any process which does not need sound system access can simply not have access to the SHM segment or sound device.
Attachment:
signature.asc
Description: This is a digitally signed message part