Document Netix security and Rust migration roadmap #15
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "docs/security-rust-roadmap"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Netix needs a durable, risk-ordered plan for replacing C/C++ infrastructure with Rust while completing its NetBSD rump/libc transition and making Jerboa central to services and policy. Adds
Roadmap.mdwith 30 dependent work packages, component disposition, immediate security prerequisites, ABI/ownership contracts, service and canonical Xen acceptance gates, and long-term core/kernel/runtime retirement tracks.The analysis distinguishes default
main, the committed rump development branch, uncommitted integration work, historical artifact evidence, and the separately inspected Jerboa runtime. Current implementation observations are not presented as production exploitability or fresh acceptance results. Primary-source research is linked beside relevant claims.VERSIONadvances from 26.10.0 to 26.10.2.Validation:
--helpsmoke passed.make binarytarget or the later development branch's canonical controller workflow; this review does not certify that development integration.82e2ac8e1f4c15e7c485098b20c0d5fdf0414934, zero commit statuses, zero Actions runs, and no required status contexts.fj pr statusfailed to decode Forgejo's empty status string. There are no green CI results to claim and no reported failing/running checks.Human review and merge required. The existing development checkout and its in-progress source changes were preserved.