Files
management/docs/issues
Thore Cimbal e3958ebe51 issues: #0110 — the hardening that only existed on the host
Two write endpoints without authentication were bound to every interface in this
repository and to a private address on the machine. The machine was right. A pull
would have silently undone it, and the only reason it did not is that git refused
over an unrelated local edit.

The ports are fixed. What is not fixed is that nothing compares the working copy
on CFGMON to the repository — it was behind by four commits and locally modified
at the same time, and neither showed anywhere. The firewall rules themselves live
in no repository at all, which makes every statement about that host's exposure a
memory rather than a source.

Measured rather than asserted, and the measurement needed care: from my own
network all three ports look shut, but so does 443, because the firewall drops
that source first. Only from a host the firewall admits does the result mean
anything — there 443 answers and 9090 does not.
2026-08-21 12:00:00 +00:00
..