On the one hand, deanonimization attacks are never entirely avoidable on unhardened targets and this one isn’t particularly sophisticated and leaks relatively little information.
On the other hand deanonimization attacks are always bad and it’s a good reminder to people of the risks they are taking. This is also slightly non-obvious behavior, even if it makes sense to the technically competent, as something like an IP grabber normally requires user interaction such as clicking a link. It’s also a vector that CF might be able to mitigate by patching the ability to query a given cache directly.
Hell, pass
init=/bin/yes
and you’ll see even more greatly reduced RAM usage!❯ ps aux | grep /usr/lib/sys | awk '{print $6}' | sed 's/$/+/' | tr -d '\n' | sed 's/+$/\n/' | bc 266516
So that’s 260 MiB of RSS (assuming no shared libs which is certainly false) for:
nohup &
needs to be fired into the sun.pkill
is not the tool I should have to use to manage my user’s daemons)For comparison the web page I’m writing this on uses 117 MiB, about half. I’ll very gladly make the tradeoff of two sh.itjust.works tabs for one systemd suite. Or did you send that comment using
curl
because web browsers are bloated?For another comparison 200 MiB of RAM is less than two dollars at current prices. I don’t value my time so low that I’ll avoid spending two bucks by spend hours debugging whatever bash scripting spaghetti hell other init systems cling onto to avoid “bloat”. I’ve done it, don’t miss it.