|
Based on my experience with using plink on Windows, I would not
recommend using putty/plink for port forwarding. It was always
slower and less reliable. I ended up using a native port of the
port forwarding portion of OpenSSH in my applications of Windows
TightVNC/SSH. The PuTTY project seems almost dead. I know everyone
uses it on Windows (as do I) for SSH terminal connectivity but the
extra issues of execing a CONSOLE mode program and then dealing with
the port issues on top of that is annoying at best. While I understand your concerns about adding additional libraries and dependencies to the project, I don't think it will be as bad as you fear with libssh. The KDE project has done a lot of work with libssh. They provide source and precompiled libs for mingw and MSVC for download. That simplifies providing these for windows. Because that is the replacement for using the command line OpenSSH client in the background on Linux, it will further insure that any Linux systems running (or capable of running) KDE 4.x (not sure the minor version it started with offhand) will have the library installed. Because of the Xorg version requirements, it will be similar distribution versions. It will not include versions like RHEL 4.x or 5.x though. I know version 6 was released but I am unsure of the length of support on 4.x and 5.x. There are a lot of things to think of as the project grows. I liked a lot of the ideas you have with increasing the VNC performance with handling multiple clients. I am very happy to see the strides that have been made with this project in such a short time. All the VNC related projects seemed very stagnant until TigerVNC came along. You have all done great work. I am not sure what areas yet but I hope I can contribute in more ways than just testing going forward. Robert On 02/11/2011 02:15 PM, DRC wrote: 2. The existing SSH tunnel capability already had the same level of external dependency, albeit a runtime dependency on /usr/bin/ssh. Granted, the new implementation makes it a build-time dependency or a dynamic library dependency instead of a child process dependency. I would go so far as asserting that libssh is a more portable dependency than a hardcoded reference to "/usr/bin/ssh".There is nothing preventing a -via option on Windows. It just hasn't been implemented yet. We could use, for instance, PLink as the tunneling process rather than /usr/bin/ssh. Also, on Unix, the VIA command line can be configured at run time to use something other than /usr/bin/ssh. --
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. |
------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
