Niklas Gustavsson wrote: > I'm probably particular thick today :-) Just to make sure I understand > what you mean. What you would like is to have an option that enforces a > client to send the AUTH command before USER/PASS, right?
First off, it's not so much about what I'd like, rather an idea born out of your response to the original poster. :) Let's backtrack for a moment... Dustin asked if it was possible to stop non-secure clients from logging in. You correctly stated that they could use implicit SSL but also added that that only forces SSL for the control socket, not the data socket. My follow up was meant to point out that if you add a configuration option to ensure AUTH is sent before LIST/etc, a user could still login without any protection, and not be warned of needing SSL until they do a LIST. However, by that time, the USER and PASS commands have been transfered in the clear. So my idea was to have that config option to reject the USER command if SSL isn't already enabled. However, I got suckered in there for a minute. What I should have asked is: why does the server not secure the data socket when using implicit SSL? This, I believe, is what the Murray draft required. If I'm wrong on that point, then my initial suggestion stands.
