Oh I love the “walk me through what I’m about to do” concept. Dry runs should be more common – especially in shell scripts…
The world would be a better place if every install.sh
had a --help
, some nice printf
’s saying “Moving this here” / “Overwrite? [Y/N]”, and perhaps even a shoehorned-in set -x
.
Hope your r/w wasn’t eaten up by the subfolder incident (that I presume happened) :P
Lots of good answers here but I’ll toss in my own “figure out what you need” experience from my first firewall funtime. (Disclaimer: I used nftables – it should be similar to ufw in terms of defaults though).
python -m http.server
– I unblocked port 8000 for personal use.I didn’t use WireShark back then, really. I think I just ran something like
which showed me a bunch of port traffic (mostly just harmless language servers).
You don’t have to dive to deep into all the “egress” and “ingress” and whatnot unless you’re doing something special. Or your software uses a weird port. (LocalSend lol)