Holiday is over, now I have fun again. No code changes. (0.38.11)
This commit is contained in:
parent
bd2d619cb9
commit
f896e1d3bf
13 changed files with 329 additions and 0 deletions
17
docs/security-and-sandboxing.md
Normal file
17
docs/security-and-sandboxing.md
Normal file
|
|
@ -0,0 +1,17 @@
|
|||
# Security and Sandboxing
|
||||
|
||||
Understand the trust boundaries and how to run Fun code safely.
|
||||
|
||||
## Trust model
|
||||
- By default, Fun code can access functionality exposed by the stdlib and any enabled extensions.
|
||||
- File and network access depend on available modules and host configuration.
|
||||
|
||||
## Running untrusted code
|
||||
- Prefer running in a container/VM with restricted filesystem and network.
|
||||
- Limit available stdlib/modules by controlling `FUN_LIB_DIR` contents.
|
||||
- Use OS-level sandboxing (seccomp, AppArmor, SELinux, chroot) where applicable.
|
||||
|
||||
## Best practices
|
||||
- Avoid running as root.
|
||||
- Validate and sanitize inputs at module boundaries.
|
||||
- Keep your build minimal; disable unneeded extensions at compile time.
|
||||
Loading…
Add table
Add a link
Reference in a new issue