|
Yeah, the PuTTY project has not really released anything since about
2007. I have done some work with libssh. I thought I had it
compiled against gnutls instead of openssl. I may need to double
check that though. I will dig into that and report back to the
list. Robert On 02/11/2011 03:22 PM, DRC wrote: On 2/11/11 1:59 PM, Robert Goley wrote: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.Yeah, in VirtualGL and TurboVNC, we use a customized build of it that has extensions to allow SSh-style port forwarding command line args and improves performance somewhat over the upstream version. I sent my patches upstream, but like you said, the PuTTY project is almost dead. They never released a follow-on version that addressed the issues we were having, so we just maintain our own.There is a real need for a native Windows (not Cygwin) version of OpenSSH.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.Well, yes and no. libssh requires OpenSSL, right? That means we have to statically link with OpenSSL in order to produce cross-compatible binaries. Static linking with OpenSSL is, I can tell you from experience, not my favorite pastime. And now, if someone wants to build a full-featured version of TigerVNC, they need OpenSSL, libssh, GnuTLS, libgcrypt, libgpg-error, libtasn1. Yuck. I really want us to reduce some of the existing complexity before we start adding more. ------------------------------------------------------------------------------ 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 --
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
