I have done some testing with the 1.2 version using DRC's provided
binaries. So far, most of it is good. I have run into a couple of
glitches though. One of them may be a problem with my understanding
of the security types parameter too. The first issue is with the security types. I am specifying " -SecurityTypes TLSVnc,VncAuth" on the server. When I connect with all client options enabled, it uses TLSVnc. When I connect with ALL TLS options unchecked, it still connects TLSAuth. Why is that? Did I not specify the server option correctly or is the client ignoring the allowed connection methods? The same thing happens with whatever I select as the first option on the server. If I select VncAuth, it never allows using TLS even if it is the next in the list. The second issue is with the numpad keys. I had seen this issue previously only with a linux viewer connecting from 1 ubuntu machine to the server running Debian with DRC's Xvnc binary. It now seems to happen with the FLTK viewer on all platforms. By default, the numlock is on both on the local workstation and in the VNC session. If you pressed the numlock key while the viewer is connected to the VNC server, it will turn the numlock off and enable the arrow keys etc. If you press numlock again, it does not enable the numbers on the numpad. It stays set to the arrow keys ONLY ON THE SERVER! The local workstation enables the numbers on the numpad. This has been a great annoyance to my users. If you use a software keyboard like kvkbd, you can re-enable the number keys but then the local workstation is the exact opposite. You have to disconnect from the server before hitting the numlock and then reconnect for them to be in sync. As a temporary workaround, I have used these xmodmap settings to force the number keys for numlock on and numlock off. #####xmodmap-numpad###### keycode 0x5A = 0 keycode 0x57 = 1 keycode 0x58 = 2 keycode 0x59 = 3 keycode 0x53 = 4 keycode 0x54 = 5 keycode 0x55 = 6 keycode 0x4F = 7 keycode 0x50 = 8 keycode 0x51 = 9 keycode 0x5B = period keycode 0x6C = Return keycode 0x56 = plus keycode 0x52 = minus keycode 0x3F = asterisk keycode 0x70 = slash keycode 0x4D = ########### The third issue has to do with the Mac app bundle. I LIKE having an app bundle and a interface that does not require X11. I usually have more than one VNC session up at a time. The app bundle only allows one connection at a time. If I click on it again, it does not relaunch a viewer. I don't see an option inside the viewer to open a second connection either. I know the latter was done by TightVNC but I am unsure if it was in the 4.x codebase. Either opening a new view from the app or a new connection from the viewer would work fine for me. Any suggestions? --
Robert Goley
![]() FOSS Implementation Specialist Toll Free: (800) 338-4984 Local: (770) 479-7933 Fax: (770) 479-4076 www.openrda.com America's only Free & Open Source fund accounting software company. |
------------------------------------------------------------------------------ Magic Quadrant for Content-Aware Data Loss Prevention Research study explores the data loss prevention market. Includes in-depth analysis on the changes within the DLP market, and the criteria used to evaluate the strengths and weaknesses of these DLP solutions. http://www.accelacomm.com/jaw/sfnl/114/51385063/
_______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel