Julien Cretin
Julien Cretin
The interpreter has (and probably often needs) some unsafe code. Fuzzing (#81) is a partial answer. MIRI is another orthogonal partial answer. Fuzzing with MIRI is probably prohibitive, but maybe...
Applet developers shouldn't need to clone the `wasefire` repo to use the host runner. In particular, it should be possible to start the host runner from the CLI #38. We...
This issue lists the conditions that a crate must meet to qualify as stable (and bump to the `1.0.0` version). ### Board API - #50 such that API extensions are...
We currently build the list of host functions dynamically when creating the scheduler. This could be done statically. We would need the following things: - A notion of linker in...
Design questions: - We probably don't want to use WebAssembly linking, because we want each applet to have its own store (see #48). This means that data would need to...
To simplify crypto testing, we could provide applets that read from USB or something test vector requests and emit responses back. This could be used to test against CAVP, Wycheproof,...
There is some duplication between stubs (#170) and the logic in the scheduler mapping from applet API to board API and the default implementations of the board API (like software...
Currently, most parts of the build are pinned to a given version using `rust-toolchain.toml` and `Cargo.lock` files. However some parts are not, essentially things installed globally, like `apt-get install`. It's...
It would be useful to have some form of user interface for debugging applets. Feature ideas: - It could be a REPL-like textual interface to type commands and/or a graphical...
All WebAssembly (dynamic) resource limits (is it only RAM?) should be configurable: - Maximum stack usage (if stack usage is bounded per function we only need to check when calling...