|
Hello Scott.
>>3.5 In the VNC PropertyTab, the user can specify what "display\port" ... > > One trouble here: the display/port data field is greyed out when I'm > using Kaboodle to start up a VNC viewer. Some servers (which I do not have > control over) on my LAN may be running on 5901, display 2, or something > else. So I need access to this data field. The display/port data field is greyed because of Kaboodle don't checked VNC server auto running. Of course, we can make display/port data enable in this case, but this don't allow make VNC session. > >7 Modification to support VNC options > >Spec: 4.2.5 Allow ONLY Kaboodle users to connect to this machine. > >Status: implemented. > >Comment: We forbade all users to connect to Vnc listener except their > >own PCs. For this we placed the string -:+MyIpAddress in value AutoHosts > >of WinVnc registry key. > > Interesting. I need to give this some more thought. If Kaboodle is > used to startup the VNC server, then setting LoopbackOnly in the registry > should be sufficient. If Kaboodle is not controlling the startup of the VNC > server, then any changes to the registry would require a server restart. > I'm not sure Kaboodle can do that...? If Kaboodle is used to startup the VNC server on PC1, Kaboodle really don't startup the VNC server at the own startup. Kaboodle listen TCP connection from other Kaboodle on PC2. When it occur, Kaboodle startup VNC server for loopback connection... I inspected different combinations of VNC server registry key WinVNC3 and it seems that only AllowLoopback=1 LoopbackOnly=0 is cool. But if there is not string -:+MyIpAddress in value AutoHosts, then other PCn machine can connect to VNC server on PC1. If we want "Allow ONLY Kaboodle users to connect to this machine" string -:+MyIpAddress is need. If Kaboodle on PC1 is not controlling the startup of the VNC, ... Kaboodle don't control VNC server on PC1 at all times. > >9. Remote VNC server password are stored... > >Status: implemented. > >Comment: Remote VNC server password is stored in registry as an encrypted > >string. This password is not sent to the network. ... When a user hits > >"connect" > >in the PropertyTab, the session is connected without the usual password > >prompt. > > Is the registry entry that stores the encrypted password set > with any non world-readable file permissions? This so. Kaboodle uses function CEncryptor::EncryptDecrypt() when passord is setting to registry. This function was plagerized from pre Akmosoft Kaboodle source code. > >10 Modification to auto-detect VNC server on LAN. > >Status: implemented for WinNT and Win2000. > >Comment: we have some problems with memory manager for Win98. > > This didn't seem to detect a VNC server on my LAN at startup. I went > thru the "check again" process and it did, however. Even when I set the server > to listen on 5911, the Viewer setup detected it correctly, and put the right > into into the port/display fields. Cool. > > However, when a server isn't detected, the only thing in the VNC > PropertyTab should be a "CheckAgain" and "Stop Check" button. Only after a > server is detected should the PropertyTab show the VNC viewer controls. It's > confusing to show those controls if there's no server. Yes, I see it problem and try to find decision. Most difficult is an event Win98. In the following letter you have written. >One more thing...I noticed that the device discovery >has started to take longer. I ran a tcpdump on a Linux machine >on my LAN, and noticed this: >05:49:40.060495 192.168.123.130.4112 > 206.13.28.12.53: 2+ PTR? >4.123.168.192.in-addr.arpa. (44) (ttl 128, id 41721) >... I want to explain all this now. At Kaboodle first startup it begin VNC running auto detection for all non Kaboodle device. For all device Kaboodle creates 100 threads. Each thread checks only one VNC server port. All these threads work simultaneously. However, first startup of Kaboodle occurs slowly. Number of this threads is (Number non Kaboodle device)*100. Too much... If we reduce the number of threads, Kaboodle first startup initialization will be executed else slowly. I attach special research project VncRunningAutoDetect to this letter. You can see how it works for different number of threads. It seems to me possible to do the following: - don't check VNC running auto detect at Kaboodle first startup. - when PropertyTab "VNC setup" is opening for PCn, Kaboodle check "was VNC running auto detect for PCn machine?". If it is not - Kaboodle check VNC running auto detect for this PCn. This well by following reasons. VNC running auto detect for one device is quickly - it seems to me that enough 0,2-0,3 second. We never have't threads count (Number non Kaboodle device)*100. Here can be 2 variants. - We save flag "was VNC running auto detect for PCn machine?" in registry and use it all time. - We save flag "was VNC running auto detect for PCn machine?" in Kaboodle session cache and use it only during one Kaboodle session. In this case Kaboodle will be have more really "VNC auto running data". What you think above? - Igor |
