<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - PulseAudio gets reliably killed upon a big number of client connections" href="https://bugs.freedesktop.org/show_bug.cgi?id=94629#c10">Comment # 10</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - PulseAudio gets reliably killed upon a big number of client connections" href="https://bugs.freedesktop.org/show_bug.cgi?id=94629">bug 94629</a> from <a class="email" href="mailto:tanuk@iki.fi" title="Tanu Kaskinen <tanuk@iki.fi>"> Tanu Kaskinen</a> <pre>One more comment... (In reply to Ahmed S. Darwish from <a href="show_bug.cgi?id=94629#c6">comment #6</a>) > Excellent. So beside a policy patchset, we also need a "handling > abusive clients" one .. there's still a very long way to go for > proper containers support ;-) I'm not sure what you mean by "proper", but having the possibility to cause a DoS on the audio system doesn't seem hugely problematic to me. The goal of hostile applications is rarely to only make the life of the user miserable. Of course it would be nice to be able to prevent that, but even if we never fix this, I don't expect there to be much trouble from security point of view. A bigger problem is that legitimate use cases may bring the audio server down (high cpu use can also be caused by a single stream with heavy processing).</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>