Date: Mon, 3 Aug 2009 15:34:07 +0300 From: "Reko Turja" <reko.turja@liukuma.net> To: "Neal Hogan" <nealhogan@gmail.com> Cc: Frederique Rijsdijk <frederique@isafeelin.org>, FreeBSD-Questions <freebsd-questions@freebsd.org> Subject: Re: ftps ? Message-ID: <BE1E18172F6745389CBD03FCE3446AA3@rivendell> In-Reply-To: <ab7b49bc0908030526t2edb123aj3adc8938fe843d02@mail.gmail.com> References: <4A76C9CF.5050100@isafeelin.org><991123400908030434p5877e2bm78db504cd06bde09@mail.gmail.com><4A76CE91.3000506@isafeelin.org><991123400908030502w1e4a16q600360f2c1c97adb@mail.gmail.com> <ab7b49bc0908030526t2edb123aj3adc8938fe843d02@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>> pure-ftpd supports TLS/SSL. >> >> I am wondering if it can do this. >=20 > I was curious about the OP's use of 'ftps" too. Perhaps, he could > explain what plain-old-ftp doesn't do and what he wants it to do. Plain old FTP transfers username/password pairs in plaintext over the = internet, as well as the actual content, which is a security hole. sftp = - the file transfer protocol included in SSH suite has been more than = adequate replacement for my needs as the traffic is encrypted and there = is no need for firewall trickery in order to get the separate = data/control connections going. Said that, I'd just use sftp, there are free text based and graphical = clients available and for the end user it handles just like regular ftp, = with added bonuses like using keys for authentication etc. -Reko
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BE1E18172F6745389CBD03FCE3446AA3>