New post: "Can We Retain the Benefits of Transitive Dependencies Without Undermining Security?" https://tratt.net/laurie/blog/2024/can_we_retain_the_benefits_of_transitive_dependencies_without_undermining_security.html
=> More informations about this toot | More toots from ltratt@mastodon.social
@ltratt See also:
CHERIoT and the supply chain
=> More informations about this toot | More toots from david_chisnall@infosec.exchange
@ltratt
I would say this needs hardware support; some kind of privilege barrier operating across regular procedure calls between components. The callee can only see its own stack frame, and heap memory allocated by itself or explicitly passed to it.
=> More informations about this toot | More toots from jannem@fosstodon.org
@jannem I broadly agree.
=> More informations about this toot | More toots from ltratt@mastodon.social
@ltratt @jannem that's broadly how wasmboxing works in Firefox to isolate some third party libraries, but without explicit hardware support https://hacks.mozilla.org/2021/12/webassembly-and-back-again-fine-grained-sandboxing-in-firefox-95/
=> More informations about this toot | More toots from tomrittervg@infosec.exchange
@ltratt I really, really enjoyed this post - it says a few things I've felt and appreciated someone else saying, and proposes several ideas I've not thought of before. Thank you for taking the time to write it.
=> More informations about this toot | More toots from konklone@me.konklone.com
@ltratt WASM is looking like a reasonable future. I expect in about a decade that software distribution will largely become WASM modules with its strong ocap security guarantees
=> More informations about this toot | More toots from gray17@mastodon.social This content has been proxied by September (3851b).Proxy Information
text/gemini