Fix harden ssl options#14
Open
asyncmind0 wants to merge 5 commits into
Open
Conversation
Owner
|
thanks! but maybe we can just allow to pass entire ssl options to httpc? so all options will be on your own and you can play with them as you want, without hardening them for all users |
Owner
|
i don't accept that, don't use formatter and allow to specify ssl options entirely. like {raven_erlang, [
{uri, "https://app.getsentry.com"},
{project, "1"},
...
{ssl, <HERE_YOU_DEFINE_YOUR_CONFIG>}
]}.because not everyone use ssl |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
https://erlef.github.io/security-wg/secure_coding_and_deployment_hardening/ssl