I am doing a project for University.
There is a monitor which does protocol verification, written in Go, I have to sandbox a closed source app with monitor .
I have chosen wasmtime as sandboxing technique.
When I tried to integrate monitor which is written in Go to wasmtime it wasn't supporting wasip2.
So I was suggested me to use wasm-tools-go
Since yesterday I am trying to integrate Wasm-tools-go
But I am unsure how to integrate.
As the first step I have added Wasm-tools-Go module to the monitor which is written in Go.
Is that all?
Then I should convert this go module to Wasm using tinyGo dev branch and then load to wasmtime?
Are these the steps?
tinygo is the only golang tooling that does wasip2 at the moment; Big Go will come along at some point. Hopefully soon. @Mossaka (Joe) will know more.... or @Randy Reddig
Hi there! Ralph is correct that wasip2 support only exists in TinyGo at the moment.
It’s under active development, with missing functionality (sockets), and known issues in TinyGo 0.33.0 related to wasip2. Your best bet is to start there or install the dev branch of TinyGo until we cut the next release.
What university are you working with on this?
Second, what protocol do you need to verify?
Randy Reddig said:
Hi there! Ralph is correct that wasip2 support only exists in TinyGo at the moment.
It’s under active development, with missing functionality (sockets), and known issues in TinyGo 0.33.0 related to wasip2. Your best bet is to start there or install the dev branch of TinyGo until we cut the next release.
What university are you working with on this?
I am studying in Saarland University,
I was given a new net package which was built after I approached here for help
https://github.com/bytecodealliance/wasm-tools-go?tab=readme-ov-file
For the time being I was given this package to make it work.
My question is on the integration which I have mentioned above.
We can use any protocol, can be fireguard, or HMAC etc
Last updated: Nov 22 2024 at 17:03 UTC