[
https://issues.apache.org/jira/browse/NET-426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13133688#comment-13133688
]
Ketan commented on NET-426:
---------------------------
Noting that can be used in production code...but for testing I am thinking of
using reflection to add the SSLSession from control channel socket to JSSE
provider's cache based on host and port. If the SSLSession is added before
handshake then session is resumed.
I did simple test based on Sun and IBM JSSE providers and it seems to work.
Again not idea solution but gets around for my needs since I can't change the
VSFTPD config which requires ssl resume on data channel.
> FTPS: Hook to customize _openDataConnection_ SSLSocket before
> startHandshake() is called
> ----------------------------------------------------------------------------------------
>
> Key: NET-426
> URL: https://issues.apache.org/jira/browse/NET-426
> Project: Commons Net
> Issue Type: Bug
> Components: FTP
> Affects Versions: 3.0.1
> Reporter: Ketan
> Priority: Critical
> Attachments: FTPSClient.patch
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> Currently in FTPSClient class, there is protected _openDataConnection_
> method, which create SSLSocket for data connection. But there is no hook to
> customize the SSLSocket before startHandshake is called.
> I need to know the remote host ip and port, which i can get for socket, and
> do custom setup to try to reuse SSL sessions from control connection socket.
> Since the socket factory uses createSocket() method, I can't just use custom
> socket factory since I don't know the host and port. I can't just override
> the _openDataConnection_() method in my class since that will call the
> startHandshake().
> So it would be nice if you can provide hook, much like _connectAction_(), but
> for data connection before handshake is started. You can pass the new data
> socket as argument to this hook method so one can get remote host and port
> information.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
