I believe that the scenario described here:
http://bugs.proftpd.org/show_bug.cgi?id=4418#c5
might capture/describe this bug, in which case, it would fall under "working as
expected".
TJ
I've tried to clarify the behavior; see:
http://www.proftpd.org/docs/modules/mod_core.html#SocketBindTight
If you are have:
SocketBindTight on
And proftpd receives a connection for which there is no
configured, the client will receive this response
500 Sorry, no server available to hand
Done; see:
http://www.proftpd.org/docs/modules/mod_core.html#MaxInstances
Cheers,
TJ
This issue with mod_ban was reported separately upstream, and fixed
there; see:
http://bugs.proftpd.org/show_bug.cgi?id=3866
Cheers,
TJ
4 matches
Mail list logo