Well, except for that fact that it would require building TigerVNC against OpenSSL, which has its own set of issues. Why not just set up a separate SFTP or SSh server on the Windows server? I use the Cygwin SSh daemon to accomplish this, but there are others that are easier to set up. There are also many free/open source SCP/SFTP/SSh client GUIs available for Windows.
Matt Campbell wrote: > Hello Peter: > > Thank you for your comments. The file transfer feature in the VNC4 > branch of TightVNC always felt flimsy to me. The UI was especially > inadequate for keyboard-only users. I made several modifications to the > UI, which I would contribute back to that branch of TightVNC if it were > still actively developed. I also agree that it would be better to use a > standard protocol; I suppose SFTP would be a good choice. > > Matt ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
