[Bug 250795] support RFB 3.3 for VNC client interoperability

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250795

--- Comment #12 from commit-hook at FreeBSD.org ---
A commit references this bug:

Author: grehan
Date: Fri Dec 18 00:38:48 UTC 2020
New revision: 368747
URL: https://svnweb.freebsd.org/changeset/base/368747

Log:
  Fix issues with various VNC clients.

  - support VNC version 3.3 (macos "Screen Sharing" builtin client)
  - wait until client has requested an update prior to sending framebuffer data
  - don't send an update if no framebuffer updates detected
  - increase framebuffer poll frequency to 30Hz, and double that when
    kbd/mouse input detected
  - zero uninitialized array elements in rfb_send_server_init_msg()
  - fix overly large allocation in rfb_init()
  - use atomics for flags shared between input and output threads
  - use #defines for constants

   This work was contributed by Marko Kiiskila, with reuse of some earlier
  work by Henrik Gulbrandsen.

  Clients tested :
  FreeBSD-current
   - tightvnc
   - tigervnc
   - krdc
   - vinagre

  Linux (Ubuntu)
   - krdc
   - vinagre
   - tigervnc
   - xtightvncviewer
   - remmina

  MacOS
   - VNC Viewer
   - TigerVNC
   - Screen Sharing (builtin client)

  Windows 10
   - Tiger VNC
   - VNC Viewer (cursor lag)
   - UltraVNC (cursor lag)

  o/s independent
   - noVNC (browser) using websockify relay

  PR: 250795
  Submitted by: Marko Kiiskila <marko at apache.org>
  Reviewed by:  jhb (bhyve)
  MFC after:    3 weeks
  Relnotes:     yes
  Differential Revision:        https://reviews.freebsd.org/D27605

Changes:
  head/usr.sbin/bhyve/rfb.c

-- 
You are receiving this mail because:
You are the assignee for the bug.