WebAssembly / WebAssembly/WASI
wasi:filesystem - correct error when trying to escalate read permissions
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 5.8k
- Forks
- 333
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 3
Description
In cases where a guest has a handle to a write-only descriptor (e.g. opened by setting only the write descriptor-flag), and tries to escalate permissions by calling open-at with the read flag, it's not clear what error should be returned.
Does it make sense to add a error write-only case to error-code similar to read-only?
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 with the WASI filesystem specification sections for open-at, descriptor flags, and error-code. Trace the write-only descriptor case when open-at requests read access, then compare the existing read-only error behavior. Done means the expected error is decided and the relevant error-code specification is updated if a new write-only case is accepted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100