Disk encryption on NetBSD - achieving secrecy
Not investment advice. Muhabbit scores how much a story may matter, not which way to trade.
NetBSD's disk encryption guidance centers on the stolen-or-lost-device threat model, prioritizing protection of user-modified directories such as /home, /var, /root, /usr/pkg, /usr/local and /etc, while treating base-system binaries like /bin/sh as non-sensitive since they are identical across installations. The article notes that true full-disk encryption is difficult without specialized hardware because the OS must load files to boot and prompt for a password, and that NetBSD stores metadata on the encrypted partition describing how to derive a secure 256-bit key from a 24-character password. It flags practical risks from shared libraries, warning that loss of directories like /usr/lib can impair the system and pointing users to the /rescue utilities that function without working shared libraries. Performance is another constraint: US-government-standardized ciphers tend to be slow in software, so many modern CPUs include hardware AES implementations, with Adiantum offered as an alternative for chips lacking them. The piece suggests a simple starting approach of encrypting /home, reflecting a strategy of protecting data that actually changes rather than the entire base system.
Muhabbit's AI wrote this summary in its own words from Hacker News's report. It can get details wrong, so check the source.
Named in this story
NetBSD, BSD, /bin/sh, /usr/lib