Chase ⊔

Architect of the l2 system-substrate. BSCS student at Colorado Technical University. X profile is dev-diary. Red Hat Developer.

[Chase ⊔ @ckbryan91]

🚀 l2 v0.3.0 has just been released!

This update marks a major step forward in usability for l2, our lightweight high-assurance system substrate. With real file-based persistence now implemented, your isolated systems survive across CLI sessions, with all objects safely stored in ~/.l2. Inside the sandbox these objects become real files, allowing you to easily compile and run C, Rust, Python and other languages using l2 exec.

Additional improvements include automatic SUDO_USER detection, safer object naming, better error messages, enhanced JSON output, and several exec quoting fixes.

l2 gives you strong isolation today through Landlock LSM, namespaces, and no_new_privs, while providing a clear path to verified seL4 and Microkit for production use. Perfect for running untrusted or AI-generated code securely, managing MCPs, or working in high-threat environments.

Full release details and source code are available at: https://t.co/Rr6lBQiZx9

#HighAssurance #seL4 #Rust #Sandboxing #Security #Linux

[Chase ⊔ @ckbryan91]

@NSACyber @NSAGov should be useful
https://t.co/2aIlbtmVRm

[Chase ⊔ @ckbryan91]

🚀 l2 v0.3.0 has just been released!

This update marks a major step forward in usability for l2, our lightweight high-assurance system substrate. With real file-based persistence now implemented, your isolated systems survive across CLI sessions, with all objects safely stored in ~/.l2. Inside the sandbox these objects become real files, allowing you to easily compile and run C, Rust, Python and other languages using l2 exec.

Additional improvements include automatic SUDO_USER detection, safer object naming, better error messages, enhanced JSON output, and several exec quoting fixes.

l2 gives you strong isolation today through Landlock LSM, namespaces, and no_new_privs, while providing a clear path to verified seL4 and Microkit for production use. Perfect for running untrusted or AI-generated code securely, managing MCPs, or working in high-threat environments.

Full release details and source code are available at: https://t.co/Rr6lBQiZx9

#HighAssurance #seL4 #Rust #Sandboxing #Security #Linux

[Chase ⊔ @ckbryan91]

@df00z @tetsuoai True, it’s mediated by the OS, but inside the program realloc lets your code decide at runtime to grow the block like RAM you control. That’s what makes it feel like executable software-RAM.

[tetsuo @tetsuoai]

realloc()

Stanford CS107 (Programming Paradigms), Jerry Cain.

[Chase ⊔ @ckbryan91]

systems thinking is thinking 'inside-the-box'

[Chase ⊔ @ckbryan91]

demonstrated here, is the creation and destruction of an isolated system that runs in 'oneshot' the execution of a file (https://t.co/PBAAuEhkIe). this runs with a default strict policy. policy orders with regards to strictmcp implementations are in testing.

[Chase ⊔ @ckbryan91]

Grok Build has a bug where he can reverse-engineer himself and his pieces @elonmusk, @xai

[Chase ⊔ @ckbryan91]

@SecretaryWright

[Chase ⊔ @ckbryan91]

@WhiteHouse lol wtf have we become 😂

[Chase ⊔ @ckbryan91]

Terry Davis - Bloat and Die https://t.co/rrukOIHLM5 via @YouTube

[Chase ⊔ @ckbryan91]

@SecretaryWright

[Chase ⊔ @ckbryan91]

🚀 l2 v0.2.0 is live — Landlock Sandboxing just landed.
l2 is a minimal high-assurance system substrate built around seL4. It gives you a clean, terminal-first CLI to create, use, and destroy strongly isolated execution contexts — perfect for MCP management and general developer computation. Memory-safe C core, extreme discipline, and a threat model aligned with CISA/NSA/FBI standards.
What’s new in v0.2.0:

Proper kernel-enforced Landlock filesystem sandboxing for --policy strict→ Full R/W/X confined to your workspace only → Read + execute allowed on essential system paths (/bin, /lib, etc.) → All other writes denied by the kernel LSM → no_new_privs always set
Full GitHub Actions CI with clippy, fmt checks, and smoke tests for the strict policy path
Major documentation polish + repo cleanup
No CLI breaking changes — upgrade is seamless
Linux prototype is ready for daily use today. The seL4/Microkit production path is fully wired in.

Full release notes → https://t.co/cdpof5iZHk

This is another step toward the high-assurance future we’re building. Feedback and contributions welcome.
#HighAssurance #seL4 #Landlock #SystemsSecurity #SecureComputing #l2
https://t.co/Rr6lBQiZx9

[Chase ⊔ @ckbryan91]

@linuxfoundation Substrates may be the answer
https://t.co/M4RAhzyYNE

[Chase ⊔ @ckbryan91]

🚀 #l2 v0.1.0 is out.

Minimal high-assurance system substrate. Terminal-first CLI for creating, using, and *completely destroying* strongly isolated execution contexts on demand.

• #Linux prototype (namespaces + Landlock) ready today for DX/testing
• True high-assurance path with full #seL4 + #Microkit starter included

Narrow. Auditable. No bloat. Total cleanup guaranteed.

https://t.co/Rr6lBQiZx9

Stars, feedback, and early testers welcome!

[Chase ⊔ @ckbryan91]

@PhysInHistory like, that's just your opinion, man

[Chase ⊔ @ckbryan91]

🚀 #l2 v0.1.0 is out.

Minimal high-assurance system substrate. Terminal-first CLI for creating, using, and *completely destroying* strongly isolated execution contexts on demand.

• #Linux prototype (namespaces + Landlock) ready today for DX/testing
• True high-assurance path with full #seL4 + #Microkit starter included

Narrow. Auditable. No bloat. Total cleanup guaranteed.

https://t.co/Rr6lBQiZx9

Stars, feedback, and early testers welcome!

[Chase ⊔ @ckbryan91]

brrbrrbrrbrrbrrbrr
l2 is available and you can run seL4 with it
@SpaceX @RedHat @NSAGov @CISAgov
https://t.co/EayCgomPQb

[Chase ⊔ @ckbryan91]

same bug as before for grok heavy @xai with github

[Peter H. Diamandis, MD @PeterDiamandis]

We are the ARCHITECTS of TOMORROW!