-
Notifications
You must be signed in to change notification settings - Fork 143
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
Sandboxing by disallowing file/network access? #937
Comments
See #921 (disabling IO should disable any side effects, though there may be bugs of course) If you want to provide a specific list of IO functions that are allowed, that is not directly possible. It ought to be possible to encode in the effect system, but that hasn't been exposed outside of the standard library (would need more work).
I'd define external |
Is it possible to disallow file/network access for sandboxing purposes? :)
The only way to interface with the outside world should be through the FFI that the host provides.
(Related to my use case #936)
Bonus question:
How can I capture stdout/stderr output so that I can send it over the network?
(E.g. as two std channels that receive each line as it gets printed, or (if that's not possible) two Strings that contain the accumulated output at the end.)
The text was updated successfully, but these errors were encountered: