Yes, MaxBacklog is read-only (as is TraceClient). It can't be negative or zero either. (The config parsing we do prevents that.)
I cannot think of any potential for abuse here. No sensitive information is leaked. The parameter simply tells the client-side API how many async dbus requests it should send before queuing additional requests on the client side, and whether to turn on debug trace for the client-side API.
We need this change in stable phone overlay too. Without it, we can't turn on client-side tracing for debugging.
Yes, MaxBacklog is read-only (as is TraceClient). It can't be negative or zero either. (The config parsing we do prevents that.)
I cannot think of any potential for abuse here. No sensitive information is leaked. The parameter simply tells the client-side API how many async dbus requests it should send before queuing additional requests on the client side, and whether to turn on debug trace for the client-side API.
We need this change in stable phone overlay too. Without it, we can't turn on client-side tracing for debugging.