On Thu, Apr 17, 2008 at 1:14 PM, stolendata. net <[EMAIL PROTECTED]> wrote: > > On Mon, Apr 14, 2008 at 6:38 AM, Almir Karic <[EMAIL PROTECTED]> wrote: > On Sun, Apr 13, 2008 at 7:37 PM, Manuel Heckel <[EMAIL PROTECTED]> wrote: > > Hi, > > > > me again here. if it's the wrong place to ask, please tell me. > > > > i still have problems with vsftp and ssl, but i don't think it's a > > problem of vsftpd. from my intern lan everything works fine, just from > > outside the connections get dropped when the TLS starts. my config: pf > > with nat and ftp-proxy for the ftp connections from inside; vsftpd on > > the same machine, listening on port 21, forced ssl. as said, from my lan > > everthing works fine, from the outside only without SSL. > > vhy not use scp or sftp? they are sane protocols that don't require > things like ftp-proxy(8) to work. > > -- > error: one bad user found in front of screen > >
Current SFTP solution of OpenSSH also lacks anything even remotely resembling the convenience VSFTPD offers for chrooted access to local users and userlists. The recent additions to OpenSSH enables administrators to jail their users, sure, but it does this in a way so clumsy that it trips over itself; solutions like hiding your users in nested dir's just to allow a shared httpd setup etc.. It's a good start, but it's very awkward. I clearly see the benefits of staying with the data-port / passive/active annoyances of FTP over TLS using VSFTPD. - SD
