-
-
Notifications
You must be signed in to change notification settings - Fork 227
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nginx ssl params config is wrong #230
Comments
I pulled that config from https://cipherli.st but I found one also at https://mozilla.github.io/server-side-tls/ssl-config-generator/ - the Mozilla one doesn't have the X-Frame-Options header so will look at switching to that config. |
No objection to using stricter cypher rules/additional security headers. Don't know if anyone uses Ghost in an embedded frame though? |
@acburdine with nginx config you need to consider compatibility vs security. By not including TLS1.0 you are preventing some Internet Explorer and older Android browsers from openning the page. But that may be a problem only if you don't use HSTS Just so you are aware. I also found that the best cipher setup is following: |
@sebgie Any input on |
refs TryGhost#230 - change x-frame-options from DENY to SAMEORIGIN - SAMEORIGIN: This setting will allow the page to be displayed in a frame on the same origin as the page itself. - background: if we deny x-frame-options, we can't export content/database
Mozillas SSL generator suggests these:
My 2cents would be following their recommendation for the best mix of client compatibility vs security! |
Running simulation with Mozilla "Intermediate" settings for nginx gives following compatibility:
For "Modern" settings compatibility is following:
Current CLI settings provided by @kirrg001 have following compatibility:
This configuration is only vulnerable to
and it's only vulnerable if TLSv1.1 or TLSv1.2 are not available on client side (older systems and browsers). So in my opinion current setting should be considered both secure and compatible. All above tests were performed assuming that TLSv1, TLSv1.1 and TLSv1.2 are enabled and that 4096 dhparam is available. |
@PaszaVonPomiot has posted a great overview of compatible browsers/devices. I would follow the official Mozilla recommendation and use the intermediate profile (no obv. vulnerability but good compatibility): https://mozilla.github.io/server-side-tls/ssl-config-generator/?server=nginx-1.10.1&openssl=1.0.1e&hsts=yes&profile=intermediate. These parameters are maintained here and we can follow necessary changes on GitHub: https://github.com/mozilla/server-side-tls. |
closes TryGhost#230 - changed SSL ciphers to Mozilla recommendation (https://wiki.mozilla.org/Security/Server_Side_TLS)
closes #230 - changed SSL ciphers to Mozilla recommendation (https://wiki.mozilla.org/Security/Server_Side_TLS)
See TryGhost/Ghost#8614 for background
in https://github.com/TryGhost/Ghost-CLI/blob/master/lib/services/nginx/files/ssl-params.conf#L12
this line:
Prevents ghost exports from working.
I'm not sure where these params came from, but they possibly need review to ensure they're not going to have other side effects.
cc @sebgie
The text was updated successfully, but these errors were encountered: