[Proftpd-user] 534 vs 220/550 response for trying to log in when TLSRequired on

Sammy Larbi <[email protected]>
Newsgroups gmane.network.proftpd.user
Message-ID <CANsBqfnAAi-jzrzWew8A2m4BWWRxYG=aw69Z7wE+_DmaAKeLTw@mail.gmail.com>
Hi,

When I require TLS, but attempt to connect with plain text, proftpd
responds first with a 200 response code, and then after the user sends
credentials, it responds with a 550 response code. I would expect a 534.

I am using ProFTPD Version 1.3.5b-4 on Debian.

Here is what the session looks like from FileZilla, when I tell it to
connect without TLS:

Status:      Resolving address of ftp.example.com
Status:      Connecting to 127.0.0.1:21...
Status:      Connection established, waiting for welcome message...
Response: 220 ProFTPD 1.3.5b Server (ftp.example.com) [::ffff:127.0.0.1]
Command: USER example_user
Response: 550 SSL/TLS required on the control channel
Error:        Could not connect to server

Why doesn't it respond immediately with 534 instead of 220, and is there a
way to force it to do so?  I would prefer if users were told they cannot
connect without TLS before they send their username.

Failing that, why doesn't it respond with 534 Could Not Connect to Server -
Policy Requires SSL instead of 550, which is supposed to be for errors
related to the file system?

And is there a way to force it to give the correct code?

Thanks for your help!

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

_______________________________________________
ProFTPD Users List   <[email protected]>
Unsubscribe problems?
http://www.proftpd.org/list-unsub.html
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.