MSWasm: Soundly Enforcing Memory-Safe Execution of Unsafe Code
cseweb.ucsd.edu · 8,818 words · saved by 1 readers
N/A
MSWasm: Soundly Enforcing Memory-Safe Execution of Unsafe Code ALEXANDRA E. MICHAEL∗ , UCSD, USA and University of Washington, USA ANITHA GOLLAMUDI∗ , University of Massachusetts Lowell, USA JAY BOSAMIYA, CMU, USA EVAN JOHNSON, UCSD and Arm Ltd, USA AIDAN DENLINGER, UCSD, USA CRAIG DISSELKOEN, UCSD, USA CONRAD WATT, University of Cambridge, UK BRYAN PARNO, CMU, USA MARCO PATRIGNANI, University of Trento, Italy MARCO VASSENA, Utrecht University, Netherlands DEIAN STEFAN, UCSD, USA Most programs compiled to WebAssembly (Wasm) today are written in unsafe languages like C and C++. Unfortunately,…
saved by
related reading
- Multiprogramming a 64kB ComputerSafely and Efficientlytockos.org
- rsmsrsms.me
- Wasmi 2.0 - Engineering of the Fastest Wasm Interpreterswasmi-labs.github.io
- Formally Verifying WebAssembly - A Soroban Case Studycertora.com
- Mitigating Memory-Safety Vulnerabilities | Computer Securitytextbook.cs161.org
- Assessing Claude Mythos Preview’s cybersecurity capabilities \ Anthropicred.anthropic.com
- A Mere Mortal's Guide to Webassemblyuptointerpretation.com
- Memory safety and ownership - Rust for C-Programmersrust-for-c-programmers.com
- NYSRGnotes.ekzhang.com
- Rewriting Bun in Rust | Bun Blogbun.com
- Build your own WebAssembly Compilerblog.scottlogic.com
- Learn Rust the Dangerous Waycliffle.com