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
What steps will reproduce the problem?
The current crypto library only supports SHA-1 and a limited subset of SHA-2 (SHA-256). While this may be enough for client-side, it would be nice to have full SHA-2 support for server-side development. This would mean support for all SHA-2 algorithms: (SHA-224, SHA-256, SHA-384, SHA-512).
What is the expected output? What do you see instead?
What version of the product are you using? On what operating system?
Dart SDK version 0.4.5.1_r21094
Please provide any additional information below.
I was looking to write a server-side program that talked to a RESTful service, but it required that all requests had a SHA-512 signature, which is not currently supported by the included Dart crypto library. I could also see this being needed for anyone doing a server-side Dart app that wants to store SHA-512 versions of users passwords.
The text was updated successfully, but these errors were encountered:
This issue was originally filed by @jwendel
What steps will reproduce the problem?
The current crypto library only supports SHA-1 and a limited subset of SHA-2 (SHA-256). While this may be enough for client-side, it would be nice to have full SHA-2 support for server-side development. This would mean support for all SHA-2 algorithms: (SHA-224, SHA-256, SHA-384, SHA-512).
What is the expected output? What do you see instead?
What version of the product are you using? On what operating system?
Dart SDK version 0.4.5.1_r21094
Please provide any additional information below.
I was looking to write a server-side program that talked to a RESTful service, but it required that all requests had a SHA-512 signature, which is not currently supported by the included Dart crypto library. I could also see this being needed for anyone doing a server-side Dart app that wants to store SHA-512 versions of users passwords.
The text was updated successfully, but these errors were encountered: