You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The ePartool has yet to adopt some more secure default settings. As mere HTTP deployments should not be supported anymore, some aspects could be upgraded:
HSTS headers
cookies only secure
protection against various Cross-Site attacks
The following additions to a .htaccess do most of it, but we should be clear whether that approach is the right place. Any thoughts/considerations?
<IfModule mod_headers.c>
Header always set Strict-Transport-Security "max-age=15552000; includeSubDomains" env=HTTPS
Header always edit Set-Cookie (.*) "$1; HTTPOnly; Secure"
Header set X-Frame-Options "sameorigin"
Header set Referrer-Policy "same-origin"
Header set X-XSS-Protection "1; mode=block"
Header set X-Permitted-Cross-Domain-Policies "none"
</IfModule>
The text was updated successfully, but these errors were encountered:
Environemet specific
These must be set per deployment as they would prevent running the application in other environments.
I think anything HTTPS related belongs in this group. Requiring HTTPS would make development needlessly complex and it would prevent using some more complicated production setups where SSL is not handled by the app server, but by some proxy or load balancer in front of it.
Also HSTS is a dangerous beast as it gets cached in user browsers and any error can therefore have really severe consequences by preventing users from accessing the site. Since https://mitwirkung.dbjr.de/mitmachen/ shares the domain with other sites, I would be rather careful setting this. Apparently it has been already though :).
These headers are not really part of the tool are such. I think the best thing we could do would be to provide some example .htaccess for HTTPS production deployments.
App specific
A while ago we did go through these, so they should be mostly OK. I tried to run Mozilla Observatory, but it tested https://mitwirkung.dbjr.de instead of https://mitwirkung.dbjr.de/mitmachen/ so the results are no really relevant to ePartool. Maybe some check-list could be done to see if everything that is applicable is set correctly?
The ePartool has yet to adopt some more secure default settings. As mere HTTP deployments should not be supported anymore, some aspects could be upgraded:
The following additions to a .htaccess do most of it, but we should be clear whether that approach is the right place. Any thoughts/considerations?
The text was updated successfully, but these errors were encountered: