# YMRTECH VPN - monthly no-log audit - November 2026

**Host:** `vpn`  
**State:** month-to-date  
**Status:** VIOLATION  
**Generated:** 2026-11-18T09:45:26Z  
**Report version:** 1

## Result

| | |
|---|---|
| Days with a signed report | 18 of 18 expected |
| Days missing (no report published) | 0 |
| Daily signatures checked / verified | 18 / 18 |
| Violations and unverifiable reports | 3 |

## Checks

| Check | Days passed | Days failed | What it asserts |
|---|---|---|---|
| `blocky:fleet:no-querylog-file` | 18 | 0 |  |
| `blocky:fleet:querylog-off` | 18 | 0 |  |
| `blocky:wg2:no-querylog-file` | 18 | 0 |  |
| `blocky:wg2:querylog-off` | 18 | 0 |  |
| `journal:no-client-tier-address` | 15 | 3 | the shipped system journal contains no client-tier address from the VPN tunnel ranges |
| `unbound:/etc/unbound-client/unbound.conf` | 18 | 0 | the effective unbound configuration contains no log-queries directive |
| `unbound:/etc/unbound/unbound.conf` | 18 | 0 | the effective unbound configuration contains no log-queries directive |

## Violations

- **2026-11-07** `journal:no-client-tier-address` - 3 client match(es) in 724 line(s) of units blocky-wg2,blocky-fleet,unbound,unbound-client since 14 days ago; 0 non-client line(s) ignored (sudo audit trail, or a fleet address: this host's own gateway, its peer's tier resolver, or the tier VIP); first: [2026-11-06 06:08:57] ERROR error on processing request:query resolution failed: resolution was not successful, no resolver returned an answer in t
- **2026-11-08** `journal:no-client-tier-address` - 3 client match(es) in 752 line(s) of units blocky-wg2,blocky-fleet,unbound,unbound-client since 14 days ago; 0 non-client line(s) ignored (sudo audit trail, or a fleet address: this host's own gateway, its peer's tier resolver, or the tier VIP); first: [2026-11-06 06:08:57] ERROR error on processing request:query resolution failed: resolution was not successful, no resolver returned an answer in t
- **2026-11-09** `journal:no-client-tier-address` - 3 client match(es) in 757 line(s) of units blocky-wg2,blocky-fleet,unbound,unbound-client since 14 days ago; 0 non-client line(s) ignored (sudo audit trail, or a fleet address: this host's own gateway, its peer's tier resolver, or the tier VIP); first: [2026-11-06 06:08:57] ERROR error on processing request:query resolution failed: resolution was not successful, no resolver returned an answer in t

## What was running

Each distinct `system_generation` seen in the month, i.e. the deployed configuration the checks ran against:

| System generation | First seen | Last seen |
|---|---|---|
| `/nix/store/0f3q87gy53jllf0fb2vc8whcs6483dl0-nixos-system-vpn-26.11.20260909.7b66dac` | 2026-11-15 | 2026-11-15 |
| `/nix/store/99iyzjp2jfqykkah3sdslbi91inmn4i4-nixos-system-vpn-26.11.20260909.7b66dac` | 2026-11-10 | 2026-11-10 |
| `/nix/store/9ymsswmi264ahwm69vmvi82ghg6zkzik-nixos-system-vpn-26.11.20260909.7b66dac` | 2026-11-09 | 2026-11-09 |
| `/nix/store/anc8d0am8hrpcd1qszqs4p5d4637vi1r-nixos-system-vpn-26.11.20260909.7b66dac` | 2026-11-02 | 2026-11-02 |
| `/nix/store/ds4b01l3s1a4dmjysfnfdc1zbl1hahjj-nixos-system-vpn-26.11.20260909.7b66dac` | 2026-11-05 | 2026-11-05 |
| `/nix/store/figah7496s9n2fc72h0cwzpm761063i6-nixos-system-vpn-26.11.20260909.7b66dac` | 2026-11-12 | 2026-11-12 |
| `/nix/store/gmpjbmbgi1y39qpj4mhw2ipyrazz9bjg-nixos-system-vpn-26.11.20260909.7b66dac` | 2026-11-07 | 2026-11-07 |
| `/nix/store/hf521h02l6gympd8ribhqqg9rnpxwsrq-nixos-system-vpn-26.11.20260909.7b66dac` | 2026-11-08 | 2026-11-08 |
| `/nix/store/inrscw0irl18c2015aahw3lwfffcry8x-nixos-system-vpn-26.11.20260909.7b66dac` | 2026-11-18 | 2026-11-18 |
| `/nix/store/m8zrrk1xdfpslqq2abdcksyr0avw8hbg-nixos-system-vpn-26.11.20260909.7b66dac` | 2026-11-13 | 2026-11-13 |
| `/nix/store/mdswczp1xagr1kza7qk40lk0m6xc8bh4-nixos-system-vpn-26.11.20260909.7b66dac` | 2026-11-03 | 2026-11-03 |
| `/nix/store/nwnd1g0hss2shpg1fllzq8h08r2g0xv5-nixos-system-vpn-26.11.20260909.7b66dac` | 2026-11-04 | 2026-11-04 |
| `/nix/store/qd4sc7zsryfclnjyy5llxsdflzk9vsig-nixos-system-vpn-26.11.20260909.7b66dac` | 2026-11-06 | 2026-11-06 |
| `/nix/store/srqhb5fn3h75j0x9fgxcdcrm8qjaky2v-nixos-system-vpn-26.11.20260909.7b66dac` | 2026-11-17 | 2026-11-17 |
| `/nix/store/xxxhjg4dgyhq2jazh7r9h1id3ljgv2mi-nixos-system-vpn-26.11.20260909.7b66dac` | 2026-11-16 | 2026-11-16 |
| `/nix/store/y6mwjww7iyym42i4d14z1cl5v3jhcrip-nixos-system-vpn-26.11.20260909.7b66dac` | 2026-11-11 | 2026-11-11 |
| `/nix/store/z692g6igx1rbmwc43p7ydqbvll0dwgil-nixos-system-vpn-26.11.20260909.7b66dac` | 2026-11-01 | 2026-11-01 |
| `/nix/store/zg8lfz93hgpgrrkj460fwqjr56ndaydc-nixos-system-vpn-26.11.20260909.7b66dac` | 2026-11-14 | 2026-11-14 |

## Retention declared by the configuration

| Data | Retention |
|---|---|
| adguard-querylog | no AdGuard instance serves on this host any more (the fleet resolver on 11.0.0.1 and the wg2 tier resolver on 172.16.41.1 are both blocky) |
| blocky-querylog | disabled on every blocky instance on this host: queryLog.type is forced to "none" by nix-config-private modules/resolver-blocky.nix (a host cannot override it; the module fails evaluation instead) |
| hermes-lcm | 90d (enforced daily by systemd.timers.hermes-lcm-retention) |
| journald | 30d local ceiling (a maximum, not an achieved window: size-bounded to 512M by NCFG-754, vpn's worst-case full-replay bound, where the ACHIEVED window is ~1-2 d and volume-dependent - 24.3 h at ~0.46 GB/day on 2026-10-07, 48.2 h at ~242 MiB/day on 2026-10-09 - so plan on ~1 d (NCFG-788); the >=3 d surface is VictoriaLogs, 14 d, whole journal shipped off-host) |
| victorialogs | 14d |
| victoriametrics | fleet store 90d; client store 30d - the per-account byte counters (clientsv_account_bytes_total, attributable to a customer's device) are routed by vmagent to vpn-mx's :8430 store which retains 30d, and dropped from the 90d fleet store (nix-config#1007) |

## Verify this report

```sh
curl -O https://vpn.ymrtech.com/logging-audit/logging-audit.allowed_signers
curl -O https://vpn.ymrtech.com/logging-audit/monthly/2026-11.json
curl -O https://vpn.ymrtech.com/logging-audit/monthly/2026-11.json.sig
ssh-keygen -Y verify -f logging-audit.allowed_signers -I logging-audit@vpn -n logging-audit -s 2026-11.json.sig < 2026-11.json
```

Every daily report can be checked the same way, and the raw machine-readable report for this month is `monthly/2026-11.json`.

- Every figure above comes from the dated daily reports in history/ ; this summary is derived from them, not a replacement for them.
- Fetch monthly/2026-11.json and monthly/2026-11.json.sig from this host together with logging-audit.allowed_signers, then run the verify command in signing_key.verify from the directory that holds them.
- Each day listed in coverage can be re-checked the same way against history/vpn-<date>.json(.sig).
- The daily report itself records which checks ran and what each observed, so a reader can audit the auditor.

Signing key: `256 SHA256:nLZOwc5NYNz4dWnTI6ZDOYi3IGsiFj9yhKEs/VzCpzY logging-audit@vpn (ED25519)`

## Notes

- state=month-to-date means the month is still running: it is rewritten on every run and its hash WILL change. state=final means the month is closed and the report is frozen - its hash must not change again.
- days_missing are coverage gaps (no report was published that day), not passes and not violations; a gap is stated rather than filled in.
- check_failures are periods during which an invariant was VIOLATED. A failing daily report is still written and signed before the audit unit fails, so a violation cannot be hidden by the failure itself.
- retention values are DECLARED from the configuration, recorded here so a change to them shows up as a diff.
- The audit runs on the hosts it audits. A reader who does not trust the host should treat it as self-reported evidence whose value comes from being signed, dated, published, and reproducible from published configuration - not from an independent third party.
