diff --git a/10-systems/hosts/tgbots.md b/10-systems/hosts/tgbots.md index e47987b..812bb54 100644 --- a/10-systems/hosts/tgbots.md +++ b/10-systems/hosts/tgbots.md @@ -6,7 +6,7 @@ owner: gmikcon status: active confidence: 100 -last_reviewed: 2026-06-05 +last_reviewed: 2026-09-10 review_interval: 90d source_of_truth: user_explicit --- @@ -16,6 +16,13 @@ ## Overview This VPS is dedicated to hosting various Telegram bots. +> **2026-09-10 audit:** an exhaustive read-only search found **no Telegram bot +> currently running or installed on this host** (no bot processes, systemd +> units, containers, cron jobs, tmux/screen sessions, project directories, or +> bot tokens anywhere on the filesystem). See +> `10-systems/bots/mardisbot.md`. The host was rebuilt around 2026-08-27; +> only the marginator stack was redeployed. + ## Technical Details - **Local IP:** 192.168.1.178 - **OS:** Ubuntu @@ -30,3 +37,22 @@ - marginator-caddy-1 — caddy:latest (reverse proxy, Caddyfile in ~/marginator) - All containers observed Up 12 days on 2026-06-05. - Backups present in ~/marginator: marginator_db_20260828_122808.sql, marginator.zip, docker-compose.yml.bak.20260828_114229 + +## 2026-09-10 bot audit (read-only, no changes made) +- Processes: no bot-like processes; only system daemons, postgres, and the + marginator gunicorn (port 5001). +- systemd: only `marginator.service`; `mardisbot.service` does not exist and + has no journal history. +- Docker: only the three marginator containers (all Up); no bot containers or + images; only compose file is `~/marginator/docker-compose.yml`. +- Cron: no user crontabs, no bot entries in /etc/cron*. +- tmux/screen: no sessions for ubuntu or root. +- Filesystem token search (`bot[0-9]{6,10}:...` pattern) over + /home /opt /srv /etc /usr/local /var: zero matches. +- Listening ports: 22 (sshd), 443/8080 (caddy), 5001 (marginator backend), + 53 (systemd-resolved), 46831 (containerd). No bot listener. +- No outbound connections to Telegram API IP ranges (149.154.x, 91.108.x). +- No python-telegram-bot/aiogram/telebot/pyrogram packages on host or in the + marginator backend container; no telegram mentions in apt history. +- Host rebuilt ~2026-08-27 (system dirs re-created Aug 27 08:20–08:39, + uptime 12 days at audit time). diff --git a/90-maintenance/pending-changes/20260910014812-1bb8f112.json b/90-maintenance/pending-changes/20260910014812-1bb8f112.json new file mode 100644 index 0000000..9f50942 --- /dev/null +++ b/90-maintenance/pending-changes/20260910014812-1bb8f112.json @@ -0,0 +1,19 @@ +{ + "id": "20260910014812-1bb8f112", + "kind": "doc", + "target": "10-systems/hosts/tgbots.md", + "summary": "Add 2026-09-10 audit note to tgbots host doc: no Telegram bot currently deployed on the host.", + "reason": "2026-09-10 live audit of tgbots found no Telegram bot deployed anywhere on the host; the host doc should record this so future agents do not assume a bot is running.", + "payload": { + "content": "---\ntitle: VPS tgbots\ntype: host\nip: 192.168.1.178\npurpose: Hosting Telegram bots\nowner: gmikcon\nstatus: active\nconfidence: 100\nlast_reviewed: 2026-09-10\nreview_interval: 90d\nsource_of_truth: user_explicit\n---\n\n# VPS tgbots\n\n## Overview\nThis VPS is dedicated to hosting various Telegram bots.\n\n> **2026-09-10 audit:** an exhaustive read-only search found **no Telegram bot\n> currently running or installed on this host** (no bot processes, systemd\n> units, containers, cron jobs, tmux/screen sessions, project directories, or\n> bot tokens anywhere on the filesystem). See\n> `10-systems/bots/mardisbot.md`. The host was rebuilt around 2026-08-27;\n> only the marginator stack was redeployed.\n\n## Technical Details\n- **Local IP:** 192.168.1.178\n- **OS:** Ubuntu\n- **User:** ubuntu\n- **Purpose:** Bot hosting\n- **Hostname:** vmk (verified via SSH 2026-06-05)\n- **Credentials:** gnexus-creds secret \"tgbots\" (id 5d8d7470-6303-46c1-8874-539cfbc49dd9); sudo uses the same password\n\n## Deployed stack (~/marginator, docker-compose)\n- marginator-backend-1 — image vlad121/marginator-backend:v2\n- marginator-db-1 — postgres:15-alpine (volume postgres_data)\n- marginator-caddy-1 — caddy:latest (reverse proxy, Caddyfile in ~/marginator)\n- All containers observed Up 12 days on 2026-06-05.\n- Backups present in ~/marginator: marginator_db_20260828_122808.sql, marginator.zip, docker-compose.yml.bak.20260828_114229\n\n## 2026-09-10 bot audit (read-only, no changes made)\n- Processes: no bot-like processes; only system daemons, postgres, and the\n marginator gunicorn (port 5001).\n- systemd: only `marginator.service`; `mardisbot.service` does not exist and\n has no journal history.\n- Docker: only the three marginator containers (all Up); no bot containers or\n images; only compose file is `~/marginator/docker-compose.yml`.\n- Cron: no user crontabs, no bot entries in /etc/cron*.\n- tmux/screen: no sessions for ubuntu or root.\n- Filesystem token search (`bot[0-9]{6,10}:...` pattern) over\n /home /opt /srv /etc /usr/local /var: zero matches.\n- Listening ports: 22 (sshd), 443/8080 (caddy), 5001 (marginator backend),\n 53 (systemd-resolved), 46831 (containerd). No bot listener.\n- No outbound connections to Telegram API IP ranges (149.154.x, 91.108.x).\n- No python-telegram-bot/aiogram/telebot/pyrogram packages on host or in the\n marginator backend container; no telegram mentions in apt history.\n- Host rebuilt ~2026-08-27 (system dirs re-created Aug 27 08:20–08:39,\n uptime 12 days at audit time)." + }, + "status": "applied", + "created_at": "2026-09-10T01:48:12Z", + "updated_at": "2026-09-10T01:48:13Z", + "applied_at": "2026-09-10T01:48:13Z", + "validation": { + "status": "ok", + "issue_count": 0, + "issues": [] + } +}