Issue 344: the screen is readable through the display server's tools
mesh/merge-gate pass: the change touches no module of the mesh's graph
mesh/repo-check pass: its merge-check.sh passed
mesh/delivery superseded: a newer head of the same pull request

This commit is contained in:
jochen
2026-10-09 12:19:54 +02:00
parent e8f0f43f1b
commit 11d261e582
@@ -74,6 +74,12 @@ note. Each gap says what is open, why it matters, and what would close it.
*Closes with:* a merge that needs the operator's own approval: a required approval on the forge from the
operator's personal account only, or an approval through ADR 0259's asks.
11. **Any caller of the mesh's tools can see the operator's screen.** The display server module's tools answer every
window's title, which can hold a mail subject or a chat's name, and can return a screenshot as data over the bus
(mesh-catalog #154). A session on another machine needs no access to the display to read it.
*Closes with:* the approval mark of research 039 for screenshot and window-listing tools, or limiting them to
the operator's own sessions.
## Why it is an issue
Each gap is a known way around a rule the mesh states. A gap that is written down can be weighed and closed. A