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

Change the default digest for new apps to SHA256 #41043

Merged
merged 1 commit into from
Jan 8, 2021

Conversation

dbussink
Copy link
Contributor

@dbussink dbussink commented Jan 7, 2021

Summary

As mentioned in #40770 (comment) we should default to SHA256 where SHA1 is used today. This switches over the ActiveSupport::Digest to use SHA256 for new applications.

It also updates the constants to always refer to and use the OpenSSL constants as well, as also discussed in that PR.

Copy link
Member

@rafaelfranca rafaelfranca left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for continue working on this. Changes looks good so far. We still need to add the the new frameworks default file that is generated inside the app like this commit c7fca84. Can you make the changes?

As mentioned in
rails#40770 (comment) we
should default to SHA256 where SHA1 is used today. This switches over
the ActiveSupport::Digest to use SHA256 for new applications.

It also updates the constants to always refer to and use the OpenSSL
constants as well, as also discussed in that PR.
@dbussink
Copy link
Contributor Author

dbussink commented Jan 8, 2021

Thank you for continue working on this. Changes looks good so far. We still need to add the the new frameworks default file that is generated inside the app like this commit c7fca84. Can you make the changes?

@rafaelfranca Added this! Also fixed some typos in the existing things that you added while I was at it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants