[jira] [Resolved] (NET-325) FTPSClient does not support pure-ftpd - data connection issues

["Sebb (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/NET-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sebb resolved NET-325.
----------------------

    Resolution: Cannot Reproduce

Current FTPSClient works fine with pure-ftpd in explicit TLS mode.

Sample command line used:

{code}
java examples.ftp.FTPClientExample -l -p TLS -T valid hostname username password
{code}

If this does not work, please re-open with further details

> FTPSClient does not support pure-ftpd - data connection issues
> --------------------------------------------------------------
>
>                 Key: NET-325
>                 URL: https://issues.apache.org/jira/browse/NET-325
>             Project: Commons Net
>          Issue Type: Bug
>          Components: FTP
>    Affects Versions: 2.0
>         Environment: Solaris 10, Windows 2003/XP, Linux (variety).  
> pure-ftpd (1.0.29) running on Linux
>            Reporter: Wade Poziombka
>         Attachments: commons-net-2.1-ftp.patch
>
>
> I do not dare attempt to declare who is right or not.  However given the popularity of pure-ftpd, FTPSClient should support it.
> It seems pure-ftpd expects the SSL handshake before sending the 150 reply to command (e.g., LIST).
> So it seems that it expects:
> > PASV | PORT
> < 227 etc.
> > LIST
> > handshake
> < 150
> ...
> < 226
> In Commons Net ftp does the following with the expectation that after the connection is accepted that the server will reply with a 150 ... reply.  However, pure-ftpd does not.  It only sends the 150 after the handshake is complete.  It means that the Socket read times out waiting for the 150.
> > PASV | PORT
> < 227
> > LIST
> < 150
> > handshake
> ...
> < 226
> I have patched 2.1 (which includes the NET-313 changes) to support pure-ftpd.  

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira