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

Recommendations on builtins/globals known to be safe or unsafe? #464

Open
zxti opened this issue Aug 27, 2022 · 0 comments
Open

Recommendations on builtins/globals known to be safe or unsafe? #464

zxti opened this issue Aug 27, 2022 · 0 comments
Labels

Comments

@zxti
Copy link

zxti commented Aug 27, 2022

Any experienced folks know if there are any builtins/globals known to be "safe" or "unsafe," at least as of current node? This can help speed up the sandboxing process for an application. Assuming we want to build a generic node web service where we isolate user requests from each other and from the "host."

I believe the default strategy is to keep running workloads, manually adding mocks for each failed standard library function (which allow exactly the specific type of invocation expected and similarly mock all returned values...somehow). But if for instance we know that fs and util should pretty much never be whitelisted, that would speed up the process.

Or for instance if we know that URLSearchParams is a safe global (its return values are also all safe), and http/https/zlib/stream are safe, then that's also helpful. With the caveat that things can change.

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

No branches or pull requests

2 participants