gzurl

5 ms·

1.
by gzurl 3y ago
Actually, that is one of the Wasm key features: being a platform-independent binary not tied to any specific HW architecture. Translating x86_64 code to arm64 requires more CPU cycles than JITting Wasm into arm64 or x86_64. Buy even more:
2.
by gzurl 3y ago
SA-CORE-2020-013 is one of them.
3.
by gzurl 3y ago
Indeed! As an example, SA-CORE-2020-013 can be mitigated with Wasm. An that one is classified as Critical.
4.
by gzurl 3y ago
Yes, sure. WasmGPT this time :-)
5.
by gzurl 3y ago
I think you missed this paragraph: The Apache HTTP server and the Drupal packages remain unchanged. However, instead of loading the libphp.so extension module, it incorporates mod_wasm.so. In addition, instead of relying on the traditional
6.
by gzurl 3y ago
Take a look at the linked article about how some PHP vulnerabilities can be mitigated with WebAssembly: https://wasmlabs.dev/articles/mitigating-php-vulnerabilities...
7.
Hardening Drupal with WebAssembly(wasmlabs.dev)
75 points by gzurl 3y ago|51 comments
8.
by gzurl 3y ago
This article explores how Drupal can benefit from the capabilities-based security model offered by WebAssembly, a portable binary format that allows execution of code in a safe and efficient manner. By deploying Drupal within a WebAssembly-
9.
by gzurl 3y ago
I didn't know about pandoc. Really useful!
10.
by gzurl 3y ago
Yes, exactly. We wrote an article here regarding PHP on Wasm that covers that: https://wasmlabs.dev/articles/mitigating-php-vulnerabilities...
11.
Mitigating PHP Vulnerabilities with WebAssembly(wasmlabs.dev)
1 points by gzurl 3y ago|0 comments
12.
Mod_WASM v0.10.0 with multi-module support(wasmlabs.dev)
4 points by gzurl 4y ago|1 comments
13.
by gzurl 4y ago
Think in the minimum container you need to run some Python code (>300MB?). Now, compare that to just the Python interpreter compiled into Wasm (25MB). If you need deploy that into different nodes, that's a huge difference. Also, Was
14.
by gzurl 4y ago
https://github.com/vmware-labs/mod_wasm
15.
by gzurl 4y ago
The "why" and the "how" here: https://wasmlabs.dev/articles/wordpress-in-the-browser/