We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently Securely exports a callback that grants access to desired intrinsics.
This decision did not take into consideration that doing operations like securely(() => anArrayProvidedByAnAttacker.sliceS()) is not really secured.
securely(() => anArrayProvidedByAnAttacker.sliceS())
Without being able to run such operation we're left with a small amount of operations that are safe to use under current design of
Securely that no longer justify the securely callback design decision.
Instead we should consider having Securely simply export a bag of intrinsics from the Securely realm (and also have it frozen #1)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Currently Securely exports a callback that grants access to desired intrinsics.
This decision did not take into consideration that doing operations like
securely(() => anArrayProvidedByAnAttacker.sliceS())
is not really secured.Without being able to run such operation we're left with a small amount of operations that are safe to use under current design of
Securely that no longer justify the securely callback design decision.
Instead we should consider having Securely simply export a bag of intrinsics from the Securely realm (and also have it frozen #1)
The text was updated successfully, but these errors were encountered: