adam/Remote-Terminal-for-MeshCore
1
0
Fork 0
mirror of https://github.com/jkingsman/Remote-Terminal-for-MeshCore.git synced 2026-08-12 03:33:03 +02:00
Code Issues Packages Projects Releases Wiki Activity

Clarify packet dedupe policy

Browse Source
This commit is contained in:
Jack Kingsman
2026-02-16 19:11:44 -08:00
parent e8ddba0131
commit 95e8bcca08
3 changed files with 12 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
AGENTS.md
+6
View File
@@ -102,6 +102,12 @@ The following are **deliberate design choices**, not bugs. They are documented i
2. **No authentication or authorization**: There is no login, no API keys, no session management. The app is designed for trusted networks (home LAN, VPN). The README warns users not to expose it to untrusted networks.
3. **Arbitrary bot code execution**: The bot system (`app/bot.py`) executes user-provided Python via `exec()` with full `__builtins__`. This is intentional — bots are a power-user feature for automation. The README explicitly warns that anyone on the network can execute arbitrary code through this.
## Intentional Packet Handling Decision
Raw packet deduplication is path-aware by design:
- Keep repeats that represent the same payload arriving via different mesh paths (this path diversity is useful).
- Drop packets that are truly identical observations (same payload and same effective pathing observation) to avoid redundant noise.
## Data Flow
### Incoming Messages