wasi-filesystem
wasi-filesystem copied to clipboard
WebAssembly
Filesystem API for WASI
On POSIX, path resolution is performed one component at a time, and `..` is resolved only after resolving all components that came before it. Opening a path such as `nonexistent/..`...
It appears that snapshot preview 1 does not have a way to change file permissions. This is important functionality for one of my use cases (a compiler that generates executables)....
I think it would be a good idea to standardise on if the file-system APIs should be case-sensitive or not and to what extent implementations should enforce case-sensitive/insensitive file-system access...
The internal struct used by `stat` calls does not have a field for the mode of the file (read/write/execute bits), and `stat`, `lstat`, `fstat`, `fstatat` all return zeros for these...
In order to advance wasi-filesystem to Phase 3, we'll need to add test coverage As discussed in https://github.com/WebAssembly/WASI/issues/384, the Wasmtime team has offered to contribute tests to seed the repo...
Any WASI runtime acting as any sort of sandbox should restrict access to unmapped paths. However, through path normalization, a path might end up "within" the sandbox. The question is,...
Some applications rely on `struct stat` to contain a `st_blksize` field to determine what size buffer to use. `filestat` doesn't currently provide this information. It may also be useful to...
Since WASI can't currently open symlinks with absolute paths, should `readlink`, fail when reading a symlink with an absolute path? That would avoid accidental leakage of host filesystem paths in...
In short, the problem is that it is difficult or impossible to implement a wasi preview1 adapter that consumes the wasip2 API (`metadataHash` and `isSameObject`) and provides the wasip1 API...
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...
