[
https://issues.apache.org/jira/browse/FTPSERVER-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörg Schubert updated FTPSERVER-244:
------------------------------------
Attachment: patch_ServerSocket_3.txt
My next try :-)
this patch works against current trunk (SVN Revision 726795). And - wow - the
fix for FTPSERVER-241 seems to make a mixed usage of SSL and unenrypted traffic
on the same port possible. Can anyone test it?
Configuration:
A passive Port range is reusable, if any of the port declarations contains an
'r'. example: <passive ports="r2505-2515" />
Support of a random passive port (<passive ports="0" />) is still broken. And
there ist no unit test yet.
> Automatically do SSL on passive ports, if Session is implict FTPS
> -----------------------------------------------------------------
>
> Key: FTPSERVER-244
> URL: https://issues.apache.org/jira/browse/FTPSERVER-244
> Project: FtpServer
> Issue Type: Bug
> Affects Versions: 1.0.0-M4
> Environment: Client PowerTCP alias DartFTP, implicit FTPS
> Reporter: Jörg Schubert
> Attachments: patch_ServerSocket_3.txt
>
>
> I had some trouble with DartFTP as client in implicit ftps mode. The client
> expects, that the data channel is automatically secure, when the control
> channel is ssl. It does not issue a PROT command.
> I know there is no clean spec for implicit ftps.
> I fixed it in the constructor of IODataConnectionFactory, but maybe this
> behaviour should be configurable:
> public IODataConnectionFactory(final FtpServerContext serverContext,
> final FtpIoSession session) {
> this.session = session;
> this.serverContext = serverContext;
> // implicitly preset security
> this.secure=session.isSecure();
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
