Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

question: sandbox for following symlinks

Open
#226 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
c

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.

Description

question

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.

Dominant language
C
Stars
272
Forks
60
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nodejs/uvwasi

All issues in nodejs/uvwasi

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.