Does FileZilla Client supports RFC 7151 or SNI for use with FTPS connections?

[mercury46]

Hi there,

I have setup a webserver for my customers with Let's encrypt certificates for the websites which works well and as expected.
Now I want my customers to connect to their subdirectories via FTPS with the same certificates.

My problem is that the FileZilla Client seems to neither send the HOST command as described in RFC7151 before the TLS handshake nor uses SNI as described in RFC 6066.
The result is that the FileZilla client does not get the correct certificate.

Example:
My customer wants to connect to their homepage "www.example.org" via explicit FTP via TLS. The TLS handshake works as expected but the customer
does not get the certificate from "www.example.org". Instead he gets the certificate from "ftp-server-from-your-hosting-provider.example.org".
Also a warning shows up that the hostname doesn't match the certificate.

My question is:
Does the FileZilla Client support RFC7151 or RFC 6066 with SNI?
If no, is it planned for the future?
If yes, how to setup the FileZilla Client to do so?

[botg]

FileZilla always uses SNI, it cannot be disabled.

[mercury46]

Thanks for the answer.

So just to be clear.
FileZilla always sends the hostname in the TLS handshake just like with HTTPS?
That means getting a wrong certificate from the server is the result of a misconfigured server?

cheers chris

[botg]

Double yes.

[mercury46]

Thank you vey much for the quick answer