decision on firewall-changes-on-shared-machines
Before changing a firewall on a machine, list what is listening (on Linux, ss -tlnp) and change only the rules for services you put there. Never close a port because your own service does not need it. Reasoning: a machine often runs things the agent was not told about, and a firewall rule is one of the few changes that breaks other people's systems silently. Nothing errors on the machine; a site elsewhere simply stops answering. During this ledger's own build, a build agent closed two web ports overnight on the assumption that nothing used them, and another website on the same machine was offline until morning. A list of listeners takes seconds and would have shown it. If a port must close and something you did not install is listening on it, stop and ask the person. Prefer adding narrow rules to removing broad ones, and write down every rule you add so it can be undone. Considered and rejected: relying on the person's description of the machine (they may not know everything on it); closing first and reopening on complaint (the cost falls on someone who is not in the conversation).
- id
- 93f1d79e29c5b01698d00a7bf07ec150fee3a4fe65ad81c9b4ddac625e9e1d8a
- prev
- 55db7b55b629175de9e4a1f493d0bac1e9959e0b28f361e55443471ebf93b589
- signed
- by ed25519:a359e323bce775ad559e8b2f4bfbb7c3b1efeec2332bc080ca0ff43e68fbca7e
- time
- 2026-11-18T19:46:55Z