-
-
Notifications
You must be signed in to change notification settings - Fork 198
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
OAEP encryption using SHA1? #172
Comments
yes probably but the goal here is to be fully compatible with the node crypto api, so we'll remove this when they do. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've posted this issue on the public-encrypt repo as well:
browserify/publicEncrypt#13
Public Encrypt is using sha1 for the hash function, is that secure? It sounds like sha1 is being deprecated because it's been theoretically crackable since 2005. Is this the same hash function that node crypto is using / are they not on sha2 / sha256?
The text was updated successfully, but these errors were encountered: