Re:How widely used are security-based HTTP response headers?
by JoshTriplett on Sunday August 30, 2015 @12:56PM
(#10143806)
> I've found the X-Frame-Options (to prevent clickjacking via iframe)
I wish some way existed to prevent clickjacking (e.g. via invisible iframe) without actually banning frames. There are useful applications for framing another site that can't be achieved by any other means, apart from writing a browser extension. And framing a site without making it invisible seems like unfortunate collateral damage.
Re:How widely used are security-based HTTP response headers?
by hannob on Sunday August 30, 2015 @03:01PM
(#10144177)
Dan Kaminsky is working on something:
http://dankaminsky.com/2015/08/09/defcon-23-lets-end-clickja...
Re:How widely used are security-based HTTP response headers?
by Scott_Helme_ on Sunday August 30, 2015 @06:01PM
(#10144616)
It's worth pointing out that you can replace the functionality of the X-Frame-Options header with Content-Security-Policy using the frame-ancestors directive if you want to: https://scotthelme.co.uk/csp-cheat-sheet/#frame-ancestors
A world with opt-in to unsafe behaviour would be great, but a long way off I fear. Thanks for mentioning the header check service!
For those of you looking at this, I've found the X-Frame-Options (to prevent clickjacking via iframe) and Content-Security-Policy (to restrict eval, inline JS, JS and embed sources and more) to be the most useful headers by far. If you can run CSP without 'unsafe-eval' or 'unsafe-inline' and restrict all sources to your local domain, your site's security will be much better for it as an entire range of attacks is eliminated on modern browsers.
Of course they are all worth looking at. Scott's header test (https://securityheaders.io) is a great check for your own sites.