Date: Tue, 23 Jan 2001 10:10:54 -0600 From: "J. Seth Henry" <jshenry@net-noise.com> To: <questions@FreeBSD.ORG> Cc: <antipode@thpoon.com> Subject: Re: questions-digest V5 #43 Message-ID: <005901c08557$110df430$9865fea9@guinevere> References: <bulk.31854.20010123000137@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an easy one - sftp. It is included in every distribution of ssh that I've seen, and works just like traditional ftp. If you go with sftp2 (ssh2), then you have a pretty darn secure daemon. A number of Windows clients even include the functionality. I use SSH's SSH2 program and it comes with a fairly useful, if no frills, FTP program. The only downside is that few normal programs can interact with it - you have to have an sftp type program to communicate. This isn't necessarily a problem, unless you have users who are using non secure ftp programs. If you are, then you can still wrap ftp, and at least limit your exposure. Seth Henry jshenry@net-noise.com Date: 22 Jan 2001 18:32:25 -0500 From: Arcady Genkin <antipode@thpoon.com> Subject: Losing FTP (last step to security) Now that I've wrapped pop3 and IMAP in SSL, my last unsecure service is FTP. What are people using as a replacement to transfer files? I am particularly interested in a method that could be recommended to my Windows users (i.e. need some graphical client for Win). Any ideas very welcome, - -- Arcady Genkin Don't read everything you believe. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?005901c08557$110df430$9865fea9>