- 0 Posts
- 5 Comments
So close! you have to do
cat < foo.txt:-) (/s)
Al, we need to optimize. Speed and efficiency to prevent Ctrl+C.
Write 16MB of zeros to the beginning of the boot device to overwrite the boot blocks (16MB being extra cautious, 8MB is fine) and if you want to double the roulette fun, have it fork in parallel and do the same thing to the EFI partition (if you have one). Extra credit: fork a 3rd time and write 16MB to the end of the disk, nuking the backup GPT structure sitting there. This can all be a fun inline “one-liner” to appeal to cut & pasters. curl pipe bashers.
It’ll happen so fast there’s no stopping it, their only way out now is to get the running system saved off that disk while it’s mounted.[1] But your nuke is invisible, how long until they find out trying to reboot? Devious Al, you’re just devious.
[1] there is a way to recover if you build identical machines, like VMs or VPSes - a tool such as gdisk can pull the table(s) off one to a file, which can be pushed onto another. We’ve recovered $customer mistakes at $ITjob doing this before, it works. It might not boot properly, but it can contain enough filesystem boundary information to be able to recover a partition manually (rescue).
Put HE (dns.he.net) in your back pocket - they run a free DNS service which includes slave (do we still call it that?) service so that you can add their resolver as an ultimate failover / failback if your self hosted DNS takes a dive for whatever reason things break in our world.
Generally, hosting your own DNS “should” mean having a primary and secondary on separate AS networks, or at least different provider routes or locations. But if you’re doing all this from home, where is the second location for DR purposes… exactly? I sure don’t have one, power goes out here everything goes dark - in the old days everyone used to do this (share out tertiary DNS to each other) but it’s become a thing of the past in today’s world. HE can help fill that gap.
To your point - I use Gcore DNS and Bunny DNS for my stuff, as I mainly use online VPSes and don’t run racks of hardware at the house. The only things I physically selfhost at home are a pair of old laptops acting as storage servers which backup all my bytes and bits from online to some SSDs.