WebAssembly / WebAssembly/WASI
Component model for filesystem access
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 5.8k
- Forks
- 333
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 3
Description
Component model can be used to introduce a more granular control on filesystem access for wasm applications, and by converse improve the interoperability between wasi packages.
A filesystem interface is just a plain text file containing a list of relative paths and permissions. A simple MyInterface filesystem interface file can contain the following lines:
path1/file1 r
path1/path2/file2 rw
file3 re
Such interface can be later imported by a wasm interpreter with a --import-file-interface command line option containing both the filesystem interface name and an absolute path containing all the files specified in the interface
--import-file-interface My interface /some/abs/path/dir/
It could be a useful feature to enable a finer way to control filesystem access.
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
No files, tests, or implementation entry points are named. Start by reviewing the proposed filesystem interface format and --import-file-interface examples, then establish the component-model integration and acceptance criteria; done requires an agreed implementation scope rather than only a proposal.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- operating-systems, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100