You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SHA-1 has a primary vulnerability of is its collision resistance, which means that it is possible to find two different messages that produce the same hash value. We would like to use SHA-256 instead, however the tls-provider doesn't currently support it.
Proposal
There is a PR already opened for awhile that several people are asking for. Could we have this merged in so we can start using sha256?