docs: record Serenity cloudflared audit
This commit is contained in:
@@ -66,8 +66,8 @@ These are live today, but they are not good long-term reasons to keep Serenity a
|
||||
These should be treated as cleanup targets unless a specific live dependency is rediscovered.
|
||||
|
||||
- `Unraid-Cloudflared-Tunnel`
|
||||
- already documented as dead/stale in repo docs
|
||||
- should be removed after one final dependency check
|
||||
- live audit on 2026-05-25 showed a remote-managed Cloudflare Tunnel with stale legacy `192.168.1.x` origins and zero observed proxied requests on the current run
|
||||
- public hostnames in its remote config now appear to be served elsewhere, so it should be removed after a brief stop/remove observation window rather than treated as an active dependency
|
||||
- `binhex-official-pihole`
|
||||
- `pihole-serenity`
|
||||
- `unbound-pihole-serenity`
|
||||
|
||||
Reference in New Issue
Block a user