iilyak opened issue #5648:
In cases where secure (or hermetic) execution environment is required it would be great to be able to disable such features as:
- networking
- time
- randomness
- host filesystem access
The capability model proposed by WASI is not sufficient in some cases. It would be great to be able to exclude code at compile time. So it is not even present in the final binary.
abrown commented on issue #5648:
If you're interested in tackling this, you may be able to plumb through a
wasi
feature disabling, e.g., thewasi-common
crate much like there are features forwasi-nn
andwasi-crypto
.
abrown edited a comment on issue #5648:
If you're interested in tackling this, you may be able to plumb through a
wasi
feature enabling thewasi-common
crate, e.g., much like there are features forwasi-nn
andwasi-crypto
.
abrown commented on issue #5648:
(I think the feature should make the
wasmtime-wasi
crate optional, which pulls inwasi-common
).
Last updated: Nov 22 2024 at 16:03 UTC