On 18 May 2011 06:35, Michael Voigt <[email protected]> wrote: > Using Commons NEt 3.0 didnt help to solve the issue. So I opened the > ticket NET-408. The ProFTPD is running on Linux (SuSE) 32bit and > 64bit.
Thanks, I saw that. > > On Tue, May 17, 2011 at 20:00, sebb <[email protected]> wrote: >> On 17 May 2011 14:34, Michael Voigt <[email protected]> wrote: >>> I'm using commons-net 2.2, Java 1.5, ProFTPD 1.3.3d, No, the server is >>> not publicly accessible, but I could send the config file. >> >> OK, could you open a JIRA issue for this with the details from this >> e-mail thread? >> >> You could attach the config to the JIRA. >> >> By the way, what OS are you using ProFTPD on? >> >> Also, might be worth trying the newly released Commons Net 3.0 - there >> were a few fixes to FTP processing. >> This is binary compatible with 2.2, so you can just replace the jar. >> >>> My code: >>> >>> FTPClient ftpClient = new FTPClient(); >>> ftpClient = new FTPSClient("TLS"); >>> >>> // this throws an exception with TLSProtocol TLSv1 >>> ftpClient.connect(host, port); >>> >>> int reply = ftpClient.getReplyCode(); >>> if (!FTPReply.isPositiveCompletion(reply)) { >>> ftpClient.disconnect(); >>> log.error("The FTP Server did not return a positive >>> completion reply!"); >>> throw new >>> FtpTransferException(ECCUtils.ERROR_FTP_CONNECTION); >>> } >>> >>> boolean loginSuccessful = ftpClient.login(userName, >>> password); >>> if (!loginSuccessful) { >>> log.error("Login to the FTP Server failed! The >>> credentials are not valid."); >>> throw new >>> FtpTransferException(ECCUtils.ERROR_FTP_LOGIN); >>> } >>> >>> ftpClient.execPBSZ(0); >>> ftpClient.execPROT("P"); >>> >>> boolean success = ftpClient.storeFile(fileName, fis); >>> if (!success) { >>> // this is false if "NoSessionReuseRequired" is not >>> set >>> } >>> >>> >>> >>> On Tue, May 17, 2011 at 12:52, sebb <[email protected]> wrote: >>>> On 17 May 2011 10:39, Michael Voigt <[email protected]> wrote: >>>>> Hi all, >>>>> >>>>> I have a problem with the FTPClient connecting to a ProFTPD server. >>>> >>>> What versions of Net, Java, ProFTPD? >>>> >>>> Is the server publicly accessible? >>>> >>>>> If the server uses the configuration option "TLSProtocol TLSv1", I >>>>> cannot connect to it at all. I recieve the following error message: >>>>> - javax.net.ssl.SSLException: Unrecognized SSL message, plaintext >>>>> connection >>>> >>>> What code are you using? >>>> >>>>> On the server side I see in the log: >>>>> unable to accept TLS connection: protocol error: >>>>> - (1) error:14094416:SSL routines:SSL3_READ_BYTES:sslv3 alert >>>>> certificate unknown >>>>> - TLS/TLS-C negotiation failed on control channel >>>>> >>>>> If the server uses the configuration option "TLSProtocol SSLv23", I >>>>> can connect to it but I cant transfer any files. In the server log I >>>>> see: >>>>> - starting TLS negotiation on data connection >>>>> - TLSv1/SSLv3 renegotiation accepted, using cipher RC4-MD5 (128 bits) >>>>> - client did not reuse SSL session, rejecting data connection (see >>>>> TLSOption NoSessionReuseRequired) >>>>> - unable to open data connection: TLS negotiation failed >>>>> >>>>> If I add the NoSessionReuseRequired parameter to the ProFTPD config >>>>> everything works fine. >>>>> >>>>> >>>>> Now my question is if it is generally possible to connect to a server >>>>> with "TLSProtocol TLSv1" or "TLSProtocol SSLv23" without the >>>>> "NoSessionReuseRequired" parameter? Could someone provide a piece of >>>>> example code for this? >>>>> >>>>> >>>>> Kind regards, >>>>> Michael >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: [email protected] >>>>> For additional commands, e-mail: [email protected] >>>>> >>>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: [email protected] >>>> >>>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
