I agree. Also, it wasn't just the implementation that was broken - the
special protocol had many problems as well. I would say that the design
was flawed from the start: If a file transfer feature should at all be
included in a VNC implementation, it should at least be based on some
existing
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
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
Hello all:
I noticed that file transfer was removed from TigerVNC about a month
ago. Why was this done, and is there any plan to bring file transfer
back? If the decision has already been explained, I'd appreciate a link
to the original explanation.
Thanks,
Matt
We may have discussed it before the list was created, because I can't
seem to find the thread in the archives. However, IIRC, the reason was
mainly that the feature was broken and we didn't have anyone who cared
about it enough to fix it and maintain it. File transfer only exists in
the Windows
