Thank you very much for your explanation and patch . I appreciate your time. On Thursday, October 1, 2020 at 7:00:27 PM UTC-4 DRC wrote:
> -alrqual only changes the quality of images sent when an automatic > lossless refresh occurs. It doesn't change the base quality of images > that the server sends. > > In the RFB protocol, the encoding type and (in the case of Tight > encoding) the compression level, quality, and subencoding types are > configurable using client-to-server messages, so the only way to forbid > clients from changing those parameters is to tell the server to ignore > those messages. There's no way to do that without modifying the > TurboVNC Server source code. I'm attaching a patch to demonstrate how > to do that. I don't have any interest in making such functionality an > official feature, but it should be relatively straightforward to > maintain a GitHub fork with this patch. > > On 10/1/20 5:22 PM, Andrew wrote: > > I'm using TurboVNC 2.2.5 and am trying to limit the total bandwidth > > all VNC sessions consume in my environment. Analysis has shown the > > "Tight + Medium-Quality JPEG" Encoding method is much easier on the > > network without sacrificing quality. > > > > What I'd like to do is enforce this encoding method and prevent users > > from changing it. I've tried the "-alrqual" parameter on the vncserver > > which works, but a user is still able to change the encoding method by > > bringing up the options menu in their viewer. > > > > Is this "lock down" currently possible? I appreciate any feedback. > -- You received this message because you are subscribed to the Google Groups "TurboVNC User Discussion/Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/turbovnc-users/ed0985e0-074d-428c-8fa5-4fde8ed3fd22n%40googlegroups.com.
