<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - memblockq: Assertion 'length % bq->base == 0' failed, pulseaudio aborts" href="https://bugs.freedesktop.org/show_bug.cgi?id=77595#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - memblockq: Assertion 'length % bq->base == 0' failed, pulseaudio aborts" href="https://bugs.freedesktop.org/show_bug.cgi?id=77595">bug 77595</a> from <a class="email" href="mailto:arun@accosted.net" title="Arun Raghavan <arun@accosted.net>"> Arun Raghavan</a> <pre>David, if I understand correctly, your concern is that someone not using libpulse could emulate our protocol and cause a server crash? There are probably a few more instances where this can happen, not the least of which is writing past the SHM boundary which I believe can cause a SIGBUS. One thing I can think of is that if we find such a situation, the assert could be converted into an "exception" that causes the sink input to be killed. I would say that this would need to be part of a larger effort to eliminate ways in which malicious clients could kill the daemon (which would need to include a definition of our trust model, etc.). In the mean time, I think we should unblock the release by patching both sides as you suggest. Do you want to write up patches (if you agree)?</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>