-
Notifications
You must be signed in to change notification settings - Fork 17
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
Converting ed25519 does not throw in browser #3
Comments
Oh yeah, here are the commands I used to test, just for reference Node:
Browser:
|
okay, what we should do, is extend https://github.com/dominictarr/chloride-test to also test for throws with invalid inputs. then make sure that everything does. |
Do you want me to look into that? There are some other compatibility issues between the browser versions and |
well, you'll get me either way, but that is where we should lock down the behavior. if they are not exactly the same then that is a bug! |
Hehe, I was thinking another venue than Github. IRC? I'm active on #stackvm and #scuttlebutt |
ah, well I don't really keep regular hours so async (github, ssb) works best for me |
Consider the following snippet:
In node the above throws an error due to the input being too long (here the secretKey is mistakenly used) but in the browser it happily continues. I'm not sure where to report this? Should I ensure the input myself instead?
The text was updated successfully, but these errors were encountered: