WebAssembly / WebAssembly/WASI
wasi:filesystem - semantics of file descriptor without permissions
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 5.8k
- Forks
- 333
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 3
Description
What happens when a guest calls open-at without read, write, and mutate-directory descriptor-flags?
I'm guessing that this would just allow them to view the directory structure - since there's no explicit permission for that - but won't let them do anything else. Is that correct?
(does it make sense to block such a case since that descriptor can't really do anything useful?)
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
Start by reviewing the WASI filesystem semantics for open-at and its descriptor-flags. Determine the behavior when read, write, and mutate-directory are all absent, including whether directory inspection remains possible and whether the combination should be rejected; done means the behavior and rationale are specified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100