-
Notifications
You must be signed in to change notification settings - Fork 359
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
Use YAML.unsafe_load when available #275
Comments
Hi @olleolleolle, it does not use Edit: As a workaround I am just using |
would be nice to have a new release with @schlumpfit proposal. |
same problem |
seems like this issue has already fixes in the psych repo follow the link below |
yes, but this gem was not modified to allow aliases |
What do you suggest to me? Maybe do not use aliases in the LDAP YML file? Or something else? |
pass aliases: true to YAML.safe_load see #276 |
Informed by ruby/psych#533 (comment), this Issue notes the availability of the YAML.unsafe_load method, in Psych 4.0.
YAML.unsafe_load
if available, ORYAML.safe_load
if available, enabling aliases and all the permitted classesYAML.load
if those methods aren't available (lower versions of Psych)Location of use:
https://github.com/cschiewek/devise_ldap_authenticatable/blob/default/lib/devise_ldap_authenticatable/ldap/connection.rb
The text was updated successfully, but these errors were encountered: