-
Notifications
You must be signed in to change notification settings - Fork 13
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
[SECURITY] Change the default to be secure by default #11
Comments
? I didn't understand you say "Why is it that this YAML parser is insecure-by-default?". Please explanation it with Ruby's yaml parser. |
The underlying parser for this gem is using the Lines 67 to 74 in a03d840
There is also the line in the README:
The YAML standard library also has a |
It's only used by |
Pull request contributed |
Hi!
Security researcher here looking into YAML parsers across the industry. Why is it that this YAML parser is insecure-by-default? Why not make it secure-by-default and then allow end-users to opt-in to the insecure variant similar to how the ruby standard library handles it currently.
The text was updated successfully, but these errors were encountered: