Closed eppfel closed 3 years ago
Good catch. While the error message is not super accurate on this one it actually points out a valid problem. ownCloud relies in some cases on iframes to work properly (also for enhanced security such as sandboxing purposes) and a policy of DENY
would break some stuff.
I'd accept a patch that adjust this warning for this case a bit. But we should warn about stuff that could break.
The code can be found at https://github.com/owncloud/core/blob/a2da7614a0516d1e1c07ef60b308645d7a8ad480/core/js/setupchecks.js#L223-L253, the unit tests at https://github.com/owncloud/core/blob/a2da7614a0516d1e1c07ef60b308645d7a8ad480/core/js/tests/specs/setupchecksSpec.js
Ok, never encountered iframes inside ownCloud, but if it could break stuff, I will change my header back to "sameorigin".
So, yeah, basically this ticket points out that the warnings are to generic. I'll gladly have a look into it in the future. Btw, thx for an awesome product!
Steps to reproduce
Expected behaviour
There should not be a warning.
Actual behaviour
A Warning is placed in the Admin panel: The "X-Frame-Options" HTTP header is not configured to equal to "SAMEORIGIN". This is a potential security or privacy risk and we recommend adjusting this setting. The warning is not incorrect as it states a "potential" risk, but it is annoying after spending 1-2 hours fixing all warnings.
Server configuration
CentOS Apache 2.2 MySQL PHP 5.6 9.0.1 (stable) fresh install Web Installer
Signing status (ownCloud 9.0 and above): No errors have been found.
List of activated apps:
Enabled:
The content of config/config.php:
Are you using encryption: no
Client configuration
Browser: Chrome 49 Operating system: MacOS 10.10.5
Logs
Browser log
I guess the security test just checks against "sameorigin", but not "deny". If some points me, where this might be fixed. I am willing to create a PR.