2 ms·
Long ago, I succeeded once to cut my own access through SSH to a remote server, after some firewall changes. That of course has required a long trip to the serv
by adrian_b 8mo ago
Long ago, I succeeded once to cut my own access through SSH to a remote server, after some firewall changes. That of course has required a long trip to the server, for physical access.
However that was good, because after that I have always been extra careful at any changes that could affect the firewall in any way. (That is not restricted to changes in firewall rules, because there are systems where the versions of the firewall program and of the kernel must be correlated, so an inconsistent update may make the firewall revert to its default state of denying all connections.)
- kqr 8mo agoI can warmly recommend the nohup-sleep-disable-cancel pattern for this, as a dead man's switch for danngerous changes. https://entropicthoughts.com/locking-yourself-out-with-firewall-config https://entropicthoughts.com/locking-yourself-out-with-firew...
- learn_more 8mo agoI previously managed a firewall via scripts which would automatically revert your update in 20 seconds unless interrupted. So if you botched it and lost access, you just had to sit tight for 20 seconds.
- navigate8310 8mo agoMikrotik has a fantastic "Safe Mode" that reverts any configuration changes that abruptly terminate your connection to the router