3 ms·
I once put an (intentionally) bad root password on a machine to be able to log in to the physical console, then configured the machine (it was supposed to be a
by Nextgrid 7y ago
I once put an (intentionally) bad root password on a machine to be able to log in to the physical console, then configured the machine (it was supposed to be a router) and put it on the Internet, forgetting the bad password.
I remembered a few hours later, gone back to rebuild the machine as I assumed it would be compromised, and sure enough, there was some crypto miner on it. Sadly for them, the machine didn't have anywhere enough processing power to make it worth it and they should've instead been smarter and made better use of it (it had a very beefy network connection so plenty of potential for DoS attacks or hosting malicious content, as well as being in a privileged position to capture potentially sensitive unencrypted traffic).
- tetha 7y agoYup. I recently setup a new VM on a new cloud provider at work and that poor thing got hammered with 2-4 authentication requests per minute from the get-go. By the time the UI of the cloud provider displayed the VM as running, there'd been 23 failed login requests already. I guess this means: if you're not careful, you might lose the VM before you can even login. Our base image now comes with a hardened sshd and raised firewalls so the first provisioning-run of the configuration management actually has to reduce the firewall protection.