News for hackers. Stuff that matters.
Re:How widely used are security-based HTTP response headers? by A010 on Sunday August 30, 2015 @11:43AM (#10143598)
I gone through his previous blog post and found the changing Server: header field. Why have to waste time for rebuilding nginx from source for that? Why not just insert 'server_tokens off' in your nginx.conf?
Re:How widely used are security-based HTTP response headers? by nly on Sunday August 30, 2015 @12:17PM (#10143689)
Because it doesn't eliminate the Server header, "off" will return "Server: nginx". Just one of several "fuck you" features in nginx.
Re:How widely used are security-based HTTP response headers? by Scott_Helme_ on Sunday August 30, 2015 @06:25PM (#10144656)
Sadly nly is right. The only other option to change this is the ngx_headers_more module, but that still requires a rebuild. I suppose that way you at least get a little more functionality for your troubles.
Re:How widely used are security-based HTTP response headers? by nly on Sunday August 30, 2015 @07:32PM (#10144769)
You also need that module to do per URI/path/regex match headers properly, because add_header + location blocks are woefully insufficient thanks to the way they are processed. This is one reason I gave up on CSP under nginx.
Re:How widely used are security-based HTTP response headers? by A010 on Sunday August 30, 2015 @12:35PM (#10143742)
Server: header makes people gone mad?
Re:How widely used are security-based HTTP response headers? by JoshTriplett on Sunday August 30, 2015 @12:53PM (#10143797)
It wastes space, and reveals unnecessary information about your server infrastructure.
Re:How widely used are security-based HTTP response headers? by FooBarWidget on Monday August 31, 2015 @12:46AM (#10145468)
As if turning it off helps. Nginx is so popular, attackers would just try Nginx-specific exploits right after trying Apache ones even if they don't know for sure whether you are running Nginx.