On Mon, Jul 15, 2013 at 2:36 PM, Gene Wirchenko <[email protected]> wrote:
> That is about as bad as source-target or target-source parameter > orderings. > > And if someone decides to write a secure FTP program, it will > probably be called SFTP regardless of its implementation. I was required > to implement such a program in my of the courses on my degree, and that is > what it was called. > Yes, it is a wretched hives of misused acronyms. For years, my ftp/ssh tool of choice on Windows was Ipswich's WS_FTP Pro, where the WS has nothing to do with secure, I think, but the program does support FTPS and SFTP, SSL and ssh respectively. Now, I run vsftpd for one of my clients, the "Very Secure File Transfer Protocol Daemon" which supports the ssh-only version of SFTP, which isn't really FTP at all. It's a mess. -- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html --- _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/CACW6n4vG+SqbrLb09cuY=ZPpNivz=ssdvmhz76ol18yxhxx...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
