Added patch from http://freshmeat.net/projects/netkit-ftp-ssl/ to the standard netkit-ftp installation ebuild. If `use ssl`, the patch is applied. Cheers, Tobias
Created attachment 5659 [details] ftp-0.17-r2.ebuild Is the DEPEND correct? Should the ebuild go into a different directory than the standard net-ftp/ftp/?
Created attachment 5660 [details, diff] tha patch! goes into net-ftp/ftp/files/ directory
Created attachment 5661 [details] Updated ChangeLog
I have added the ebuild to portage. Just one minor typo. It is currently marked unstable.
Ah, that reminds me... Has anyone a server to test it? I tried it with one of our company internal servers (Serv-U with SSL support turned on). It didn't work. It it working for anyone?
When failing with SSL did it fall back to unencrypted authentication? Any error messages on either the client side or server side which might clue you in to what the problem was?
I am currently in the process of adding an ssl enabled netkit ftpd package to portage. It will be added as net-ftp/ftpd. As I test and release the package into portage I will post here.
I have added net-ftp/ftpd to portage which is the netkit linux-ftpd package with ssl support added. You can try setting up that server and then connecting with the ssl enabled ftp... let me know if things work for you.
I tried it with FTPD from portage. It works. Fallback works ok if there is not SSL available at the remote ftp-server. Anyway, it does not work with my test SSL-enables Serv-U ftp-server. It tries to negotiate SSL, fails and aborts: 220-BST FTP Server ready... Name (ftp.xxx.ch:tsa): ftpupdate 234 AUTH command OK. Initializing SSL connection. 431 Unable to negotiate secure command connection. Login failed. 421 Service not available, remote server has closed connection Anybody any idea for that problem? Else, it seems to work.
I know this isn't a Serv-U support forum... but here are some ideas... my first thought is maybe it is expecting rsa encryption or something. Can you change options for SSL connections?
