TJ Saunders

Here's the [regression test I added/wrote](https://github.com/proftpd/proftpd/pull/639), for asserting the `FEAT` response lines are properly CRLF-terminated.

You have a separate `` section for your SFTP settings. And due to the way that you have `mod_ban` configured, those `mod_ban` settings are _not_ in a `` section, which...

In that case, you might try: ``` LoadModule mod_ban.c BanEngine on BanTable /var/run/proftpd/ban.tab BanControlsACLs all allow user ftpadm BanEngine on BanLog /var/log/proftpd/ban.log # If the same client reaches the MaxLoginAttempts...

Thanks for the detailed bug report! For these scanner connections, can you tell if they are only sending the `USER` command (for _e.g._ "admin"), or do they appear to hang...

One way to tell about the above question is to use `ps auxwww` (especially as root); ProFTPD updates the process title for each session with its current/recent command. This means...

Thanks! For that normal user session, did the client eventually send the `PASS` command (to complete the authentication), or did it just send `USER`, and then do nothing?

OK. I'm poring over the code base, to see what else might be happening here. In the mean time, the next time you see one of these stuck/unkillable processes, can...

@jpfinger Thanks for that info, that helps! The next time you can, can you run `strace -f -p -t -T`? The additional `-t -T` options will add the wall clock...

Thanks! From that trace output, we _do_ see that the `SIGARLM` signal is being sent to the process every 5 secs. None of the hardcoded default timeouts are 5s; @jpfinger...

OK, great. I'll work through the `mod_ctrls` code, with an eye toward newly forming connections/sessions, see if anything turns up. In the mean time, for the _next_ time you see...