Skip to content
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

Securely should consider a redesign of how it exports access to frozen intrinsics #4

Open
weizman opened this issue Aug 18, 2022 · 0 comments

Comments

@weizman
Copy link
Member

weizman commented Aug 18, 2022

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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant