<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Gobi: WebAssembly as a Practical Path to Library Sandboxing · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1912.02285/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/1912.02285/feed.xml" rel="self" type="application/rss+xml" /><item><title>Gobi: WebAssembly as a Practical Path to Library Sandboxing — mentioned by afiori</title><link>https://news.ycombinator.com/item?id=43025050</link><guid isPermaLink="false">urn:hackerpapers:mention:1912.02285:43025050</guid><pubDate>Wed, 12 Feb 2025 13:11:35 GMT</pubDate><description>&lt;p&gt;I think that looking at it in terms of Embeddability is more useful compared to portability. In the sense that compiling C to any language is easily done without too many problems, what wasm allow is to have a secure and performant interface with that language. For example IIRC one of the first inclusions of wasm was to sandbox many of the various codecs that had regular security vulnerabilities, in this Wasm is neither the first nor the only approach, but with a combination of hype and simplicity it is having good success. as in https://arxiv.org/abs/1912.02285&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1912.02285/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CR</category></item></channel></rss>
