Server crashes if a client tells it to update stream rate when the stream doesn't support that
@tanuk
Submitted by Tanu Kaskinen Assigned to pul..@..op.org
Description
I haven't tried this in practice, but it seems that the server doesn't check whether the sink input's or source output's resampler supports rate changes when a client sends a request to change the stream's rate. When using libpulse, invalid rate changes are filtered at client side, but a malicious client can talk to the server without using libpulse.