Skip to content

docs: fix inaccuracies in README #139

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
zvonkok merged 1 commit into from
Feb 24, 2026
Merged

docs: fix inaccuracies in README #139

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 2 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ recovery mechanisms—if GPU initialization fails, the VM powers off. This
│ NVRC (PID 1) │
│ │
│ 1. Set panic hook (power off VM on panic) │
│ 2. Mount filesystems (/proc, /dev, /sys, /dev/shm) │
│ 2. Mount filesystems (/proc, /dev, /sys, /run, /tmp) │
│ 3. Initialize kernel message logging │
│ 4. Start syslog daemon │
│ 5. Parse kernel parameters (/proc/cmdline) │
Expand Down Expand Up @@ -154,7 +154,6 @@ cargo llvm-cov --all-features --workspace

# Fuzzing
cargo +nightly fuzz run kernel_params
cargo +nightly fuzz run mount_parsing

# Static analysis
cargo clippy --all-features -- -D warnings
Expand All @@ -167,7 +166,7 @@ cargo deny check
NVRC operates with a defense-in-depth security model appropriate for
confidential computing:

1. **Minimal Attack Surface**: 9 direct dependencies, statically linked
1. **Minimal Attack Surface**: 7 direct dependencies, statically linked
2. **Fail-Fast**: Panic hook powers off VM on any panic (no undefined states)
3. **Read-Only Root**: Filesystem becomes read-only after initialization
4. **Module Lockdown**: Kernel module loading disabled after GPU setup
Expand Down
Loading