Greg Kurtzer开发的实验性项目Ginux完成了重大架构调整,从原本可直接通过UEFI启动的独立Rust内核,转变为运行在普通Linux进程中的用户空间内核 1。原有的独立内核代码已永久保留在bootable-kernel分支中,当前的活动开发重点已完全转向用户空间模式 1。这一转变旨在通过定义显式且版本化的接口契约,为隔离的Linux实例提供受控的系统调用拦截与模拟,而非追求完整的Linux ABI兼容性 1。
Ginux的核心机制利用seccomp过滤器将受管系统调用发送至ptrace停止点,由Ginux决定是进行模拟(Emulate)、中介(Mediate)还是拒绝(Deny)这些请求 1。该项目的设计哲学故意且选择性地打破完整Linux ABI的保证,这与Linus Torvalds名言“And we simply do not break user space.”形成对比 1。目前默认模式下允许contract-approved的sched_yield直接在主机Linux执行,而在Paranoid模式下,所有系统调用都必须经过用户空间决策 1。
需要明确的是,Ginux并非User-Mode Linux (UML),也不是成熟的gVisor替代品或VM级别的隔离边界 1。该软件仍处于研究阶段,未获得独立安全认证,因此不适用于生产工作负载,主要作为研究原型和AI代理的沙箱隔离方案存在 1。其当前参考开发环境基于macOS arm64,通过QEMU TCG启动Rocky Linux 10主机来运行Ginux 1。
Greg Kurtzer has restructured his experimental project, Ginux, shifting its primary development focus from a standalone Rust kernel to a userspace kernel operating within standard Linux processes. 1 While the original architecture—which allowed direct booting via UEFI—remains preserved in a dedicated bootable-kernel branch, active development is now centered on this new userspace paradigm. 1 The core mechanism relies on seccomp filters to route managed system calls to ptrace stop points, where Ginux determines whether to emulate, mediate, or deny each request based on explicit, versioned interface contracts. 1
The design philosophy of Ginux intentionally diverges from traditional Linux compatibility guarantees, selectively breaking full Linux ABI support to prioritize controlled isolation over universal compliance. 1 This approach contrasts with Linus Torvalds’ directive that "And we simply do not break user space," which the project cites to highlight its selective disruption strategy. 1 Ginux is distinct from User-Mode Linux (UML) and does not claim to be a mature alternative to gVisor or a replacement for virtual machine-level isolation boundaries. 1 Instead, it serves primarily as a research prototype and a sandboxing solution for AI agents. 1 The current reference development environment runs on macOS arm64, using QEMU TCG to launch a Rocky Linux 10 host running Ginux. 1 In default mode, contract-approved operations such as sched_yield are executed directly on the host Linux kernel, whereas a Paranoid mode forces all system calls through userspace decision-making. 1 The software remains in the research stage, lacks independent security certification, and is explicitly not intended for production workloads. 1
评论
还没有评论,欢迎留下第一条。