Problem setting up TLS -> bad server or bad client? about suppaftp

[veeso]

The server must respond 234 to AUTH command as stated in the RFC https://www.rfc-editor.org/rfc/rfc4217.
In particular, this section https://www.rfc-editor.org/rfc/rfc4217#section-12.1 explains the flow and the 234 response makes the client start the TLS negotiation.

Could it be the server actually doesn't support TLS?

[svet-b]

Yeah I suspected the server's behavior is not standards-compliant. And am not surprised, given the nature of the device.

The server does support FTPS - in fact it requires a secure connection - and as I mentioned, I'm able to access data using wget (with an ftps://... URL), and it doesn't seem to complain. But I guess the wget is more lenient towards behavior like this.

Anyway, I was able to work around this using an implicit FTPS connection on another port, which seemed to work without issue (thanks also for the help there!). So on balance, I wouldn't steer you towards accommodating for pathological behavior like this :). Will go ahead and close this.