-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
Proposal: std/crypto #8006
Comments
I think before we do a std/crypto we should first have webcrypto api implemented |
I don't see WebCrypto in Deno Q4 roadmap, but we need to have at least bcrypt right now, it is very popular and used to hash passwords (it is necessary for almost any Deno web server) |
I would like to add god_crypto to the list as another third party module which tries to use WebCrypto if available. |
The problem is getting crypto stuff right is difficult, that is why we still dont have webcrpyto even tho it is quite important. for that same reason, i think we should hold off having something like std/crypto. |
WASM is possible for both of them UPD: Possible for both algorithms, not modules i linked |
I know it is. but the main issue remains: we dont have someone knowledgeable about cryptography. |
The Q4 roadmap is the current priorities of the core team, it is not everything for Q4. WebCrypto would be preferred over any |
I might get to it, chime in on the original issue. |
Dont mean to reopen a dormant issue, but just wanted to chime in for future reference: @ssslambda I recently started a new project to extend Deno STD (it does not replace STD, but extends it). It encourages the addition of functionality that exists in other standard libraries (PHP, Go etc.), and also allows for functionality that benefits from being in a standard library rather than in third party modules. One example is the crypto package which provides Argon2 and Bcrypt, and other password hashes can be submitted by PR. Here is the link: https://jsr.io/@stdext/crypto |
We already have bcrypt and argon2 modules on /x, it would be nice to have them in std just like in golang, also i think both of them (and others too) can be implemented via wasm for better perfomance
The text was updated successfully, but these errors were encountered: