question: sandbox for following symlinks
Open
Nobody has claimed this yet.
question
- Dominant language
- C
- Stars
- 270
- Forks
- 60
- PR merge metrics
- No merged PRs in 30d
Description
It looks there is differences about handling symlinks between uvwasi and wasmtime.
Assuming #224 was merged and given the file path is /var/dir/file and sandbox root is /var/dir:
| Link Target \ Runtime | wasmtime | uvwasi | (memo) |
|---|---|---|---|
/var/dir/file |
NG | OK | wasmtime prohibits absolute paths without exception |
./file |
OK | OK | |
../file |
NG | NG | not in the sandbox root |
../dir/file |
NG | OK | wasmtime prohibits relative paths referencing a path that once deviates from the root of the sandbox |
I'd like to know whether this is expected behavior for uvwasi.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the assumptions around merged issue #224, then trace uvwasi's symlink and sandbox path handling while comparing the listed cases with wasmtime. Done means establishing whether uvwasi's behavior is expected; any implementation change and regression coverage would need maintainer guidance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100