4 ms·
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
by mvip 14y ago
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)?
- nodata 14y agoWhy care? If it runs, it runs.
- mvip 14y agoYes, until it runs out of memory and you need to reboot it.
- xentronium 14y agoWhy should it run out of memory?
- mvip 14y agoIt's Apache. It's what it does best.
- xentronium 14y agoComputers aren't magic. Apache httpd isn't magic. The only reason it can run out of memory is misconfiguration.
- mvip 14y agoWho 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.