Cool. I think the safe way to do it is much more complicated than just turning on the existing SHM vector.
>From what I understand it should work like so... Client connect to stream or dgram socket and (post auth) establishes that both parties believe they are on he same host and server offers to create SHM buffers for the client to use. The client may close the socket once SHM is setup, if it's done. Server should be able to query the socket, worst case using ident, to see what user is on the other end and set perms appropriately. The server might trust the client to supply perms and does so while applying a mask for sanity purposes. SHM buffers are per socket connection/pid and a single pid can ask for more than one, with some upper limit defined to prevent DOS. This adds more commands into the PA server and client, but I feel that both modes would benefit from a more robust SHM system. Having more than a single thread(client/server threads makes for a minimum of two) introduces locking concerns that just add latency. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1007866 Title: System mode: SHM avaliblity. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1007866/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
