-
Notifications
You must be signed in to change notification settings - Fork 283
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
Possible security flaw in your Solar Designer bcrypt implementation #39
Comments
It seems your C-implementation is not subject to this specific security flaw. You should however consider to produce |
reedloden
added a commit
to reedloden/bcrypt-ruby
that referenced
this issue
Mar 11, 2014
* Fixes bcrypt-ruby#39, bcrypt-ruby#80 * Include new tests from upstream (fixes bcrypt-ruby#84)
reedloden
added a commit
to reedloden/bcrypt-ruby
that referenced
this issue
Mar 11, 2014
* Fixes bcrypt-ruby#39, bcrypt-ruby#80 * Include new tests from upstream (fixes bcrypt-ruby#84)
reedloden
added a commit
to reedloden/bcrypt-ruby
that referenced
this issue
Mar 11, 2014
* Fixes bcrypt-ruby#39, bcrypt-ruby#80 * Include new tests from upstream (fixes bcrypt-ruby#84)
+1 |
reedloden
added a commit
to reedloden/bcrypt-ruby
that referenced
this issue
Feb 12, 2015
* Fixes bcrypt-ruby#39, bcrypt-ruby#80 * Include new tests from upstream (fixes bcrypt-ruby#84)
samcday
pushed a commit
to atlassian/bcrypt-ruby
that referenced
this issue
Feb 15, 2017
* Fixes bcrypt-ruby#39, bcrypt-ruby#80 * Include new tests from upstream (fixes bcrypt-ruby#84)
Fixed in #182 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Could you please answer me the following question:
http://security.stackexchange.com/questions/12132/could-the-bcrypt-ruby-binding-be-vulnerable
The text was updated successfully, but these errors were encountered: