Hold fire on what I said before. I am still in learning mode as this is
all new to me.
I had made a basic assumption that if I set "C" or "P" in the
ftpClient.ProtLevel then that would be enough to be incorporated into
the FTP connect mechanism. However not so is it. I have to manually
execute ProtAsync after the client has connected.
So now we move one step further on. The "Clear" mode works and I can
connect. If I select "Private" then I get errors and cannot connect. Now
I have to sort out certificates and things. I'll get back to you if I
find out anything that might be relevant to ICS.
The one thing I have found is that when I execute the featAsync, I do
not see the PROT in the list of supported extensions. When I look at the
source code, you are looking for "PROT C" or "PROT P". This server only
returns "PROT". There is a simple fix at the ICS client end, but not
sure yet if ICS truncates the response early on, or the server isn't
sending it correctly.
On 20/12/2017 12:09, Angus Robertson - Magenta Systems Ltd wrote:
Also if I set the PROT to C, both the listAsync and getAsync
responses are encrypted. If PROT is set to P, only the getAsync
response is encrypted.
That does not seem correct, C should not use SSL atall. I'll put this
on the list to look at, but it may be several weeks, or longer, none of
this has changed in many years and it's low priority.
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be