

For some reason my mobile client didn’t make the article link immediately obvious. That’s actually really interesting. Apparently I was under the same common misconception. So the shell in this case is choosing to continue after detecting the flush.
For some reason my mobile client didn’t make the article link immediately obvious. That’s actually really interesting. Apparently I was under the same common misconception. So the shell in this case is choosing to continue after detecting the flush.
Ctrl+d terminates input on stdin to your currently running program or shell.
I’m pretty sure I ran this on a PS3.
I may be misremembering. It may have had a smaller drive initially.
Pentium 200mmx, 32 mb ram, and I think a 5gig hard drive with windows 95. I don’t remember the original display adapter, but later it had a voodoo banshee put in it. We also upgraded the CPU to one of those evergreen technologies k6-2 400 MHz. Later we switched to windows 98 and a bigger hard drive. I think we must have upgraded the RAM too, but I don’t remember. It was a true ship of Theseus.
Edit: also don’t remember the original sound card but I think it ended with a sound blaster live with the emu10k chip.
You should turn off ssh password logins on external facing servers at a minimum. Only use ssh keys, install fail2ban, disable ssh root logins, and make sure you have a firewall limiting ports to ssh and https.
This will catch most scripted login attempts.
If you want something more advanced, look into https://en.m.wikipedia.org/wiki/Security_Technical_Implementation_Guide and try to find an ansible playbook to apply them.
Who wants some wang?
Reporting!
I beat it by kiting some of the shotgunners to come past the imps. 3 Easy kills.
People who want to shave still say this sometimes.
Wait until they find out about Ansible.