News for hackers. Stuff that matters.
Re:HTTP Security headers you should be using by tptacek on Thursday January 23, 2014 @11:18AM (#7109069)
Tell me, which of the four headers he talked about --- CSP, XFO, XCTO, and HSTS --- are going to cause serious problems for a blog?
Re:HTTP Security headers you should be using by pornel on Thursday January 23, 2014 @11:46AM (#7109251)
CSP would be useful defense in depth if the blog has comments and an admin interface on the same domain or subdomain within TLD/public suffix — XSS in a comment could lead to session fixation/hijacking.

XFO also might be useful if the blog has predictable layout of the admin interface — logged-in blog admin could be tricked via clickjacking to perform potentially undesirable actions.

Re:HTTP Security headers you should be using by michaelmcmillan on Thursday January 23, 2014 @12:39PM (#7109665)
The directory entries at http://ibuildings.nl/robots.txt suggest that they're hosting much more than a blog on that domain.

Edit: As others pointed it out, it's a Drupal installation. Trusting Drupal to be 100% safe in regards to malicious attacks is not a good idea. I know this is nitpicking, it is however still ironic.

http://www.cvedetails.com/vulnerability-list/vendor_id-1367/...

Re:HTTP Security headers you should be using by yeukhon on Thursday January 23, 2014 @12:42PM (#7109688)
It's a drupal-powered site. It's no different from WP though IMO.
Re:HTTP Security headers you should be using by yeukhon on Thursday January 23, 2014 @12:16PM (#7109474)
At least he should enable XFO if he doesn't want to be framed.

His HTTPS endpoint is not trusted by the browser, either self-signed or missing some intermediary cert... If he wants to enable the contact form for business inquiry or personal inquiry, might be worthwhile to get some $10 cert? If he already ahve gotten that far to get a 443 port enabled.

XCTO is pretty cheap to enable and doesn't hurt. The only problem is IRRC IE has a different MIME list then Firefox and Chrome.

It's pretty cheap to enable some of these security headers, just as it is relatively easy to disable some of the server-type headers (x-powered-by e.g, which apparently he doesn't have it exposed I think)