Microsoft open-sources LiteBox, a security-focused library OS
1–10 of 239 posts
Re: Microsoft open-sources LiteBox, a security-focused library OS
#2LiteBox is a sandboxing library OS that drastically cuts down the interface to the host, thereby reducing attack surface. It focuses on easy interop of various "North" shims and "South" platforms. LiteBox is designed for usage in both kernel and non-kernel scenarios.
LiteBox exposes a Rust-y nix/rustix-inspired "North" interface when it is provided a Platform interface at its "South". These interfaces allow for a wide variety of use-cases, easily allowing for connection between any of the North--South pairs.
Example use cases include:
- Running unmodified Linux programs on Windows
- Sandboxing Linux applications on Linux
- Run programs on top of SEV SNP
- Running OP-TEE programs on Linux
- Running on LVBSRe: Microsoft open-sources LiteBox, a security-focused library OS
#3From the GitHub page: LiteBox is a sandboxing library OS that drastically cuts down the interface to the host, thereby reducing attack surface. It focuses on easy interop of various "North" shims and "South" platforms. LiteBox is designed for usage in both kernel and non-kernel scenarios. LiteBox exposes a Rust-y nix/rustix-inspired "North" interface when it is provided a Platform interface at its "South". These inte…
Reddit discussion: https://www.reddit.com/r/linux/comments/1qw4r71/microsofts_n...
Project lead James Morris announcing it on social.kernel.org: https://social.kernel.org/notice/B2xBkzWsBX0NerohSC
Re: Microsoft open-sources LiteBox, a security-focused library OS
#4Re: Microsoft open-sources LiteBox, a security-focused library OS
#5[flagged]
Re: Microsoft open-sources LiteBox, a security-focused library OS
#6[flagged]
https://news.ycombinator.com/item?id=45077654 - "Generated comments and bots have never been allowed on HN"
Re: Microsoft open-sources LiteBox, a security-focused library OS
#7Re: Microsoft open-sources LiteBox, a security-focused library OS
#8The cargo.lock file is 2200+ lines long. Did they spend a reasonable amount of time auditing these dependencies?