Skip to content
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

Preload digest/sha2 to avoid thread safe error. #30705

Merged
merged 1 commit into from
Sep 25, 2017

Conversation

frodsan
Copy link
Contributor

@frodsan frodsan commented Sep 25, 2017

Summary

I got this error in production using Puma in multi-threaded mode:

RuntimeError: Digest::Base cannot be directly inherited in Ruby
from active_support/security_utils.rb:23:in `variable_size_secure_compare'
from active_support/security_utils.rb:23:in `hexdigest'
from active_support/security_utils.rb:23:in `digest'

Looks like Digest uses const_missing to load Digest::SHA256 (https://github.com/ruby/ruby/blob/trunk/ext/digest/lib/digest.rb#L8)

Other information

@rails-bot
Copy link

Thanks for the pull request, and welcome! The Rails team is excited to review your changes, and you should hear from @eileencodes (or someone else) soon.

If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.

This repository is being automatically checked for code quality issues using Code Climate. You can see results for this analysis in the PR status below. Newly introduced issues should be fixed before a Pull Request is considered ready to review.

Please see the contribution instructions for more information.

@frodsan frodsan changed the title Use thread-safe manner to load Digest::SHA256. Preload digest/sha2 to avoid thread safe error. Sep 25, 2017
@matthewd
Copy link
Member

Let's fix

(any others?) at the same time.

@frodsan
Copy link
Contributor Author

frodsan commented Sep 25, 2017

@matthewd cool! I was wondering if it's better to use OpenSSL implementation? Like:
https://github.com/rails/rails/blob/master/actionpack/lib/action_controller/metal/request_forgery_protection.rb#L395

I got this error in production using Puma in multi-threaded mode:

```
RuntimeError: Digest::Base cannot be directly inherited in Ruby
from active_support/security_utils.rb:23:in `variable_size_secure_compare'
from active_support/security_utils.rb:23:in `hexdigest'
from active_support/security_utils.rb:23:in `digest'
```

Looks like Digest uses const_missing to load Digest::SHA256 (https://github.com/ruby/ruby/blob/trunk/ext/digest/lib/digest.rb#L8)

- https://bugs.ruby-lang.org/issues/9494
- ruby/ruby@c02fa39
@matthewd matthewd merged commit 5e56d2b into rails:master Sep 25, 2017
@matthewd
Copy link
Member

I don't think there's any advantage to using the OpenSSL one. (Whereas I assume it's used there because it's being passed to OpenSSL HMAC, not called directly.)

@frodsan frodsan deleted the use-digest-thread-safe branch September 25, 2017 20:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants