-
Notifications
You must be signed in to change notification settings - Fork 151
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
Consider adding an API that takes the nonce size and tag size as parameters #544
Comments
Alternatively an operation similar to I think that could be done as a completely additive change. I think it's otherwise nice to have monomorphized tag sizes for type safety reasons in every other use case than "I am implementing a dynamic API for a scripting language which needs to choose the tag size completely at runtime" |
Hm but that means that the tag size still needs to be configured statically right? |
No, it would take a slice, and return an error if it wasn't a valid size |
We are building a Node.js runtime for the browser so you can run Node.js entirely in your browser without relying on cloud servers. That means we run arbitrary code and right now it's only possible to specify the nonce size and tag size statically via types so we are forced to always call
from_slice(...)
. Ideally we can create it once and not rely on a match that matches nonce size and tag size, e.g.So it'd be nice if we could do
from_slice(key, nonce_size, tag_size)
.The text was updated successfully, but these errors were encountered: