You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Jesús González <je...@vmware.com> on 2023/02/01 14:15:23 UTC

Re: mod_wasm: Contributing Upstream to Apache

Yes, the usage of Wasm for filters makes a lot of sense. This is why I previously mentioned the Envoy’s proxy-wasm spec<https://github.com/proxy-wasm/spec>, which is essentially an ABI specification for running WebAssembly in proxies. Beyond Envoy, you can find similar approaches in Nginx<https://wasmedge.org/book/en/use_cases/frameworks/mesh/wasm-nginx-module.html> and in APISIX<https://github.com/apache/apisix/blob/master/docs/en/latest/wasm.md>. One of our long term goals is to implement this specification for Apache itself.

mod_wasm’s initial goal is to allow running unmodified apps under WebAssembly in Apache (i.e.: WordPress, Drupal, etc.). Having said that, it is also a great fit to expose the internal Apache APIs, enabling safely building Apache modules using ANY language, not just filters but any functionality. Basically, a lot of the functionality you need to use mod_lua and mod_perl (or having to write your own C module) but language independence and with other benefits inherited by running Wasm code: sandboxing security, running at almost native, etc.

Re: mod_wasm: Contributing Upstream to Apache

Posted by Jesús González <je...@vmware.com>.
Great! Thanks Steffen.

Re: mod_wasm: Contributing Upstream to Apache

Posted by Jesús González <je...@vmware.com>.
Hola!

We just released a mod_wasm security update (v0.11.2) to address a recent CVE (low security). More details in the changelog<https://github.com/vmware-labs/mod_wasm/blob/main/CHANGELOG.md>.

Cheers,
Jesús


Re: mod_wasm: Contributing Upstream to Apache

Posted by Jesús González <je...@vmware.com>.
Hola!



We have released recent versions of mod_wasm allowing Wasm modules to return any output type via stdout, including binaries with non UTF-8 bytes sequences or \0 NULL terminators in the middle, among other fixes (see CHANGELOG<https://github.com/vmware-labs/mod_wasm/blob/main/CHANGELOG.md> for details).


These new versions allowed us to run new fully functional and unmodified applications (such as Drupal) in a safe WebAssembly environment. We will release a demo soon and a post with all the details.



We believe mod_wasm is getting ready for a v1.0.0 release. So, we really would like to get feedback from the HTTPD committers here. Still our plan is contributing this module upstream and helping to maintain it.



Cheers!

Jesús


Re: mod_wasm: Contributing Upstream to Apache

Posted by Jesús González <je...@vmware.com>.
Hola!

We just released a mod_wasm security update (v0.10.3<https://github.com/vmware-labs/mod_wasm/releases/tag/v0.10.3>) to address two recently disclosed CVEs (one critical) of Wasmtime, the WebAssembly runtime mod_wasm uses.

Further details can be found in this article<https://wasmlabs.dev/articles/wasmtime-6-0-1-security-update/> and in the mod_wasm changelog<https://github.com/vmware-labs/mod_wasm/blob/main/CHANGELOG.md>.

Let us know if you find any issues.

Cheers!
Jesús