We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Seems to expect you to hardcode ssl_key_file_name, ssl_cert etc. and does not make use of the keystone dir
Its not very modern user will only get a C on the ssl_labs test if the users deploys as is. We must do better that that.
Some stuff is missing e.g strong DHE param generation.
The text was updated successfully, but these errors were encountered:
Address issue #96
d2e1052
No branches or pull requests
Seems to expect you to hardcode ssl_key_file_name, ssl_cert etc. and does not make use of the keystone dir
Its not very modern user will only get a C on the ssl_labs test if the users deploys as is. We must do better that that.
Some stuff is missing e.g strong DHE param generation.
The text was updated successfully, but these errors were encountered: