lkn
/
anvillm
Archived
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Include debug logs in observability references

This commit is contained in:
Levi Neely 2026-03-18 23:54:27 +01:00
parent 3f271122ec
commit 1746fc4c5c
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/code-execution-security-guide.md
View File

@ -144,7 +144,7 @@ Validation is basic pattern matching. Not comprehensive - relies on sandbox for
**Mitigations**:
1. 9P socket permissions (Unix socket, user-only)
2. anvilsrv enforces access control
3. Observability via event stream and mailbox archives
3. Observability via event stream, mailbox archives, and debug logs
**Residual risk**: If subprocess has 9P access, it has the same capabilities as any 9P client. This is by design.

6
docs/code-execution-security.md
View File

@ -34,7 +34,7 @@ The code execution pattern allows agents to write and execute bash code in a iso
┌─────────────────────────────────────────┐
│ 9P Operations │
│ - Unix permissions │
│ - Event stream / mailbox archives │
│ - Event stream / mailbox archives / debug logs │
└─────────────────────────────────────────┘
```
@ -248,7 +248,7 @@ if agentID != session.AgentID {
}
```
3. **Observability**: State changes visible via event stream, message history via mailbox archives
3. **Observability**: State changes visible via event stream, mailbox archives, and debug logs
4. **Operation Whitelist**: Only allowed operations exposed
```go
@ -559,7 +559,7 @@ The code execution pattern provides strong security through multiple layers:
2. **bash Subprocess**: Process-level isolation
3. **Landlock LSM**: Kernel-level enforcement
4. **Resource Limits**: Prevent exhaustion
5. **Observability**: Event stream and mailbox archives
5. **Observability**: Event stream, mailbox archives, and debug logs
**Security Posture**: Data isolation and explicit control over information flow via sandboxed subprocesses.