Security - WebAssembly

A community dedicated to discussing the big picture: humans, technology, and the connections between them, with an eye towards avoiding techno-dystopian outcomes.

Background:

Awesome Code Sandboxing for AI. Contribute to restyler/awesome-sandbox development by creating an account on GitHub.

An overview of the sandboxing landscape, and some experiments with Deno.

Learn how to secure Blazor WebAssembly apps as single-page applications (SPAs).

RFC process for Bytecode Alliance projects. Contribute to bytecodealliance/rfcs development by creating an account on GitHub.

How we solved a strange issue involving the guts of Chrome and the Go compiler.

WASM: universal application runtime Last summer, fresh off my last freelance gig, I was catching up with my friend Asim, the founder of the widely popular microservices company, Micro at one of our favourite coffee shops in London. We would end up meeting almost every week talking about the presence and the future of technology. But that day our conversation turned into something that we had not talked about for a long time: Web assembly (WASM).

Discussions around memory safety often focus on choice of language, and how the language can provide memory safety guarantees. Unfortunately, choosing a language is a decision made at the start of a project. Migrating an existing C or C++ project to a safer language is much harder than starting a new project in a safe language1. I’m not going to say this is impossible, or that you can’t or shouldn’t migrate existing programs to safer languages. And sometimes people just do things in open-source, and that’s part of the fun of it.

V8 features a lightweight, in-process sandbox to limit the impact of memory corruption bugs

Contribute to amlalabs/amla-sandbox development by creating an account on GitHub.