Security improvements for Kibana/Nginx #169
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This branch includes one change and one addition related to security and Kibana's web server:
Disallow the SSLv3 protocol which is vulnerable to POODLE. Update the allowed TLS cipher suite according to current best practices.
Reference: https://raymii.org/s/tutorials/Strong_SSL_Security_On_nginx.html.
Add a new attribute,
['elkstack']['config']['kibana']['prepare_ssl']
which allows users to disable thekibana_ssl
recipe if they wish to configure this themselves (including providing their own certificate and private key). The default istrue
, meaning the behaivor stays as it is by default.