News for hackers. Stuff that matters.
Re:Backdoor in the TP-Link routers by mvip on Friday March 15, 2013 @05:28AM (#5379777)
The major vuln aside -- are they seriously running Apache the router? "/usr/bin/httpd" sure looks to me like Apache (but could of course be anything). Heard of Nginx or Lighttpd (or countless other lightweight web servers)?
Re:Backdoor in the TP-Link routers by nodata on Friday March 15, 2013 @05:35AM (#5379788)
Why care? If it runs, it runs.
Re:Backdoor in the TP-Link routers by mvip on Friday March 15, 2013 @05:44AM (#5379806)
Yes, until it runs out of memory and you need to reboot it.
Re:Backdoor in the TP-Link routers by xentronium on Friday March 15, 2013 @05:58AM (#5379836)
Why should it run out of memory?
Re:Backdoor in the TP-Link routers by mvip on Friday March 15, 2013 @06:24AM (#5379874)
It's Apache. It's what it does best.
Re:Backdoor in the TP-Link routers by xentronium on Friday March 15, 2013 @08:08AM (#5380115)
Computers aren't magic. Apache httpd isn't magic. The only reason it can run out of memory is misconfiguration.
Re:Backdoor in the TP-Link routers by mvip on Friday March 15, 2013 @09:35AM (#5380497)
Who said anything about magic? Apache's default config is crappy and it's a bloated web server. It will bring down any VPS to swap of death unless you lower MaxClient etc with even moderate amount of traffic.

More modern web servers (and more lightweight) don't have that problem. They work for most configuration out-of-the-box (and perform better).

I don't know how Apache is configured on this particular router, but I can spot ten httptd-processes in on the process listing. So yes, Apache is likely both a bad choice to start with and beyond that, it is also poorly configured.