Repository navigation
The threat model says what a compromised net zone still reaches, what limits it, and what stays by design - #311
Merged
Merged
Conversation
… limits it, and what stays by design
…s administrator may use, and where module firmware comes from
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Merge after #305 and #306. Two of the checks it names,
radio-recarriedanduplink-state-reset, arrive with them; both are in linux-distro-7d's batch.What was wrong. The threat model said of a compromised net zone only that it "gets no zone's files and not
vault". It did not say what such a zone can still reach or deny, what limits it, or what is kept that way on purpose. Each of those is now settled in the tree and proven by a check.What changed. A new section in
docs/threat-model.md, "Compromised net zone", under "Network attacker". Each item is one sentence:dhcpcd-separatedanddnsmasq-unprivileged: the parsers run without the zone's root;fetch-and-sntp-no-caps: the update fetcher and the SNTP client hold no capability;net-cpu-max-setandnet-zone-sysfs-nics-only: the zone's CPU and what its/sysshows;nic_writing_ioctls_are_refused: NIC-writing ioctls are refused;uplink-renamed-plain,uplink-state-resetandradio-recarried: what it leaves on a NIC does not reach the next net zone.zone-source-pinned: send as another zone;bridge-ports-closed: reach what else listens in the net zone;zone-flows-capped: fill the connection-tracking table;dns-cache-offanddns-counters-hidden: learn another zone's lookups.How it is checked. Docs only, nothing in the image changes, so CI and a non-author read stand in for a Distro run. Every check named is in the zones suite on main once #305 and #306 merge, or, for the ioctls, in kryptikd's unit tests.