Feature #219

dropbear should run out of xinetd

Added by Dave Täht almost 2 years ago. Updated about 1 year ago.

Status:Closed Start date:08/02/2011
Priority:Normal Due date:
Assignee:Dave Täht % Done:

0%
Category:Networking Spent time: 0.50 hour
Target version:1st Public Cerowrt release

Description

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
before RC5.

History

#1
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.

#2
Updated by Dave Täht over 1 year ago

Why are there bugs I can't CLOSE?

#3
Updated by Dave Täht about 1 year ago

  • Category set to Networking

#4
Updated by Dave Täht about 1 year ago

  • Status changed from Resolved to Closed

dropbear could use some improvement, yes, both on oom, and on max-cpu behavior.

but the oom bug is separate.

Also available in: Atom PDF