Skip to content

Support digest with SHA-256 and SHA-512/256 as per RFC 7616 #48

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom
Open
spaskalev opened this issue Sep 16, 2017 · 3 comments · May be fixed by golang/crypto#192
Open

Support digest with SHA-256 and SHA-512/256 as per RFC 7616 #48

spaskalev opened this issue Sep 16, 2017 · 3 comments · May be fixed by golang/crypto#192

Comments

@spaskalev
Copy link

RFC 7616 defines a new algorithm header field and specifies SHA-256 and SHA-512/256 as valid options. It still supports MD5 for backwards compatibility, but explicitly recommends against it.
@spaskalev spaskalev mentioned this issue Sep 16, 2017
Open
This was referenced Oct 6, 2021
Open
Closed
@creeble
Copy link

creeble commented Mar 15, 2022

Curious about this pull request and/or alternatives.

It seems like this particular PR includes SHA-256 and SHA-512/256, and uses standard libraries. But I can't tell if it's actually complete?

Is there any movement on this? Has anyone tested @spaskalev 's PR?

@spaskalev
Copy link
Author

IIRC it worked but it has been nearly five years since I used it :)

@rojer
Copy link

rojer commented Jan 24, 2024

fwiw, popular browsers now support it too, including chrome - https://bugs.chromium.org/p/chromium/issues/detail?id=1160478

# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

x/crypto/crypt/md5crypt: MD5 APR1 implementation of crypt(3). abbot/crypto
3 participants
@rojer @spaskalev @creeble