https://bz.apache.org/bugzilla/show_bug.cgi?id=68773
--- Comment #1 from Jaikiran Pai <[email protected]> --- Hello Florian, it appears that you have sufficiently narrowed this down to what's causing the issue. From what you state (and based on my very superficial knowledge of FTPS), it appears like for the data channel to be secured, the client has to issue a "PROT P" command which implies PRIVATE data channel and enables encryption. Right now, the FTPS task doesn't issue that command. I have committed a experimental change in our Ant master branch which now introduces a "useSecureDataChannel" attribute on the "ftp" task. This attribute can be (optionally) set to "true" (only) when "useFtps" is set to "true". Internally, when this attribute is true and useFtps is also true, then the task, in this experimental change will now issue a "PROT P" command. The other way to do it probably would be to expose a "execPROT" attribute which takes either of "C", "E", "S", "P" values. I haven't fully thought whether that would be more convenient. In any case, I don't have a way to test this change. Would you be willing to test this either by building Ant master branch and using that Ant version or by using our nightly unreleased build from https://ci-builds.apache.org/job/Ant/job/Ant_Nightly/lastCompletedBuild/artifact/ (job number 215 and higher should have this change). In that experimental build, you would have to additionally set useSecureDataChannel="true" attribute in your ftp task usage. Can you give that a try and see if it works. If it does, then I can decide how we want to expose this as an attribute, plus update the manual for that task. -- You are receiving this mail because: You are the assignee for the bug.
