dropbear should run out of xinetd
|Assignee:||Dave Täht||% Done:||
|Category:||Networking||Spent time:||0.50 hour|
|Target version:||1st Public Cerowrt release|
I had planned to do this for a while now. Our dropbear is already patched to be runnable out of xinetd, I have half a patch to make xinetd oom-killer aware, and there's half a xinetd sensors package around that locks out people (bots, actually) entirely that attempt telnet to the router.
I feel uncomfortable skipping the oom-killer patch, but as fiddling with dropbear and doing it wrong would be bad, getting dropbear to work out of xinetd first, correctly, strikes me as the least risky, so I MAY given time, move dropbear to xinetd and get the sensors package working
Updated by Dave Täht almost 2 years ago
- Status changed from New to Resolved
- Assignee set to Dave Täht
dropbear now runs out of inetd.
Also, sensors are configured on telnet and ftp attempts to the router.