Merge remote-tracking branch 'origin/main' into fix/deleting-an-account-tells-the-account-service

# Conflicts:
#	SECURITY.md
This commit is contained in:
Paul Hitt
2026-09-21 17:42:35 -04:00
+30
View File
@@ -39,6 +39,36 @@ does not, and how to report a problem.
Open a confidential issue on this repository, or mail the address on
flamenet.io. A first reply inside seven days. Nothing here pays a bounty.
## ⚠️ The lattice, and the half of it that is not enforced
Carried forward from `525d7f7`, which landed on main while this branch was
open. The labels it describes moved into the messenger with everything else,
so the gap is still real and this is not the place it will finally live: see
flamenet-messenger ios#65 and android#15.
**The ★-property is not enforced.** What is enforced is *no read up*: an object
your session label does not dominate is not visible, and by default writes
happen at exactly the session label. What nothing enforces is the other half of
Bell-LaPadula. A principal cleared to a high label may open a session at a lower
one and write there, carrying down what they read above it. No client stops
this, because a session label inside a principal's clearance range is a
legitimate session.
🔴 This is the half the model exists for. No-read-up stops somebody reaching
material above them, which most systems get right. No-write-down stops the
material leaking *downward through a person who is allowed to see it*, which is
the threat a lattice is built to contain.
⚠️ Deliberate, and not an oversight: a rule enforced on one client and not the
other is worse than the gap, and strict enforcement with no downgrade path
produces a workaround culture. Doing it properly means an explicit downgrade
action with an audit trail. Until that exists, this is written down rather than
implied away.
So "implements Bell-LaPadula" is too round a word for what exists. It
implements the **simple security property**, not the **★-property**, and naming
a model is itself a claim about which of its rules hold.
## Scope note
This repository was also a file service, Flamenet Files, whose security model