Re: TigerVNC clipboard-encoding UTF-8

[Yang Yang <yy...@icloud.com.INVALID>]

Hi Ben,

Have you got a solution on this? I ran into the same issue.

Also, it seems this is related to [GUACAMOLE-1043] vnc clipboard support unicode - ASF JIRA (apache.org) <https://issues.apache.org/jira/browse/GUACAMOLE-1043>, can someone else shed some light?

Thanks,
Yang 

> On Apr 19, 2022, at 23:21, Ben Sheppard <An...@mandiant.com.INVALID> wrote:
> 
> Ive circled back on this issue, and still cant seem to get it working. I found a PR in libvncserver which enables UTF-8 via a compilation flag:
> 
> https://github.com/LibVNC/libvncserver/pull/468 <https://github.com/LibVNC/libvncserver/pull/468>
> 
> I recompiled the library with this flag off latest master, then recompiled guacamole and x11vnc against that version, then replaced TigerVNC with x11vnc. If I connect to my server with TigerVNC Viewer 1.12.0, I get a log line that shows the extended clipboard support is enabled:
>  
> 19/04/2022 14:22:17 Client Protocol Version 3.8
> 19/04/2022 14:22:17 Protocol version sent 3.8, using 3.8
> 19/04/2022 14:22:17 Battling with something for -norepeat!! (1 resets left)
> 19/04/2022 14:22:17 Disabled X server key autorepeat.
> 19/04/2022 14:22:17   to force back on run: 'xset r on' (2 times)
> 19/04/2022 14:22:17 rfbProcessClientSecurityType: executing handler for type 2
> 19/04/2022 14:22:20 Enabling full-color cursor updates for client 192.168.1.229
> 19/04/2022 14:22:20 Enabling X-style cursor updates for client 192.168.1.229
> 19/04/2022 14:22:20 Enabling NewFBSize protocol extension for client 192.168.1.229
> 19/04/2022 14:22:20 Enabling ExtDesktopSize protocol extension for client 192.168.1.229
> 19/04/2022 14:22:20 Enabling LastRect protocol extension for client 192.168.1.229
> 19/04/2022 14:22:20 Enabling ExtendedClipboard extension for client 192.168.1.229
> 19/04/2022 14:22:20 Using compression level 2 for client 192.168.1.229
> 19/04/2022 14:22:20 Using image quality level 8 for client 192.168.1.229
> 19/04/2022 14:22:20 Using JPEG subsampling 0, Q92 for client 192.168.1.229
> 19/04/2022 14:22:20 Using tight encoding for client 192.168.1.229
> 19/04/2022 14:22:20 Sending rfbEncodingExtDesktopSize for size (1280x1024)
> 19/04/2022 14:22:20 Client requested resolution change to (1280x762)
> 19/04/2022 14:22:20 Sending rfbEncodingExtDesktopSize for size (1280x1024) resize prohibited
> 19/04/2022 14:22:22 client 1 network rate 94.5 KB/sec (47962.5 eff KB/sec)
> 19/04/2022 14:22:22 client 1 latency:  186.9 ms
> 19/04/2022 14:22:22 dt1: 0.0041, dt2: 0.1053 dt3: 0.1869 bytes: 10335
> 19/04/2022 14:22:22 link_rate: LR_DIALUP - 186 ms, 94 KB/s
> 19/04/2022 14:22:26 created selwin: 0xa0002c
> 19/04/2022 14:22:26 called initialize_xfixes()
>  
> When I connect via Guacamole I don’t get that:
>  
> 19/04/2022 14:25:28 Client Protocol Version 3.8
> 19/04/2022 14:25:28 Protocol version sent 3.8, using 3.8
> 19/04/2022 14:25:29 Using compression level 3 for client 172.20.2.1
> 19/04/2022 14:25:29 Enabling X-style cursor updates for client 172.20.2.1
> 19/04/2022 14:25:29 Enabling full-color cursor updates for client 172.20.2.1
> 19/04/2022 14:25:29 Enabling cursor position updates for client 172.20.2.1
> 19/04/2022 14:25:29 Enabling KeyboardLedState protocol extension for client 172.20.2.1
> 19/04/2022 14:25:29 Enabling NewFBSize protocol extension for client 172.20.2.1
> 19/04/2022 14:25:29 Enabling SupportedMessages protocol extension for client 172.20.2.1
> 19/04/2022 14:25:29 Enabling SupportedEncodings protocol extension for client 172.20.2.1
> 19/04/2022 14:25:29 Enabling ServerIdentity protocol extension for client 172.20.2.1
> 19/04/2022 14:25:29 Using ZRLE encoding for client 172.20.2.1
> 19/04/2022 14:25:34 copy_tiles: allocating first_line at size 41
> 19/04/2022 14:25:34 client 1 network rate 1647.5 KB/sec (36115.0 eff KB/sec)
> 19/04/2022 14:25:34 client 1 latency:  0.5 ms
> 19/04/2022 14:25:34 dt1: 0.0081, dt2: 0.0057 dt3: 0.0005 bytes: 22626
> 19/04/2022 14:25:34 link_rate: LR_LAN - 1 ms, 1647 KB/s
> 19/04/2022 14:25:39 created selwin: 0xa0002c
> 19/04/2022 14:25:39 called initialize_xfixes()
>  
> I do see the UTF-8 warning from guacd in syslog:
>  
> Apr 19 14:25:28 dev-01 guacd[3650841]: Using non-standard VNC clipboard encoding: 'UTF-8'.
> 
> In practice, Im still getting ??? when I copy unicode (Cyrillic), has anyone gotten this working with VNC? Is there a known working configuration (Guacamole settings + VNC server) that are known working that I can use?
>  
> From: Ben Sheppard <Andrew.Sheppard@mandiant.com.INVALID <ma...@mandiant.com.INVALID>>
> Reply-To: "user@guacamole.apache.org <ma...@guacamole.apache.org>" <user@guacamole.apache.org <ma...@guacamole.apache.org>>
> Date: Friday, January 28, 2022 at 12:58 PM
> To: "user@guacamole.apache.org <ma...@guacamole.apache.org>" <user@guacamole.apache.org <ma...@guacamole.apache.org>>
> Subject: [EXTERNAL] TigerVNC clipboard-encoding UTF-8
>  
> CAUTION: This email originated from outside of Mandiant. Do not click links or open attachments unless you recognize the sender and know the content is safe.
> Hi all,
>  
> Im running TigerVNC server 1.12.0 in Ubuntu 20.04 and was able to verify UTF-8 bidirectional clipboard works using their official TigerVNC Viewer in OSX.
>  
> However, when using Guacamole 1.4.0 with clipboard-encoding=UTF-8 configured for the connection, all the UTF-8 characters still end up as ? characters. The Guacamole documentation leads me to believe this will work as Ive verified it works standalone.
>  
> Ive found some older/newer threads with conflicting information, and Im not sure if what Im attempting to do is supported, or if I have something misconfigured.
> 
> Any help is much appreciated, thanks!
> This email and any attachments thereto may contain private, confidential, and/or privileged material for the sole use of the intended recipient. Any review, copying, or distribution of this email (or any attachments thereto) by others is strictly prohibited. If you are not the intended recipient, please contact the sender immediately and permanently delete the original and any copies of this email and any attachments thereto.
> CAUTION: This email originated from outside of Mandiant from a third party. Please take extra precaution clicking on any embedded links or downloading and opening file attachments. If you feel this is a suspicious email, please use the ‘Report Phishing’ button in your Outlook toolbar. 
> This email and any attachments thereto may contain private, confidential, and/or privileged material for the sole use of the intended recipient. Any review, copying, or distribution of this email (or any attachments thereto) by others is strictly prohibited. If you are not the intended recipient, please contact the sender immediately and permanently delete the original and any copies of this email and any attachments thereto.