You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit fb46a3f
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: docs/STATUS-REPORTING.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -104,6 +104,7 @@ Covered threats:
104
104
Residual risks:
105
105
106
106
- compromise of one controller exposes that controller's reporting key and permits forged reports for that identity until rotation;
107
+
- ordinary runner jobs are already host-root-equivalent through the Docker socket and can read any host-local reporting key; this channel prevents cross-controller impersonation but does not attest a controller against malicious code already running on that controller. Isolate job Docker onto a separate trust boundary before treating reports as adversarial to job code;
107
108
- compromise of the receiver exposes retained status and all receiver-side reporting keys;
108
109
- HMAC keys are symmetric; use a managed asymmetric identity service later if receiver compromise becomes part of the impersonation threat model;
109
110
- the read bearer token is suitable for the backend foundation, not browser distribution. A future console should terminate user authentication before this API.
0 commit comments