Something tells me I need to update my security…
Is there a bit more context to this? This just shows a bunch of image file names.
Scrot is a screenshot tool in Linux that you can run from the command line, I think the implication is that OP didn’t do this on purpose so “may have been hacked”, or had something heavy fall on their “Prnt Scrn”.
Found a shitload of screenshots in my home directory after logging in for some maintenance. It’s been a while since checking out the server and seeing only 50MB of space
What are they?
About 15 gigs of screenshots from something pressing down my prtscrn button unknowingly, lol
At least I hope that’s what happened.
World largest scrotum dataset for training dick pic ai
Looks like scrot pngs from here
Or you host a LOT of scrot pics.
With Reddit all weird, I gotta make sure my uploads are in safe hands
Scrot is a Linux screen clipping/screenshot utility. It creates images with that name. My guess is you’re using that either directly or indirectly for screenshots.
https://opensource.com/article/17/11/taking-screen-captures-linux-command-line-scrot
If you aren’t ever taking screenshots, it’s possible some malware may be using that software and just doesn’t bother cleaning up after itself. It’d be pretty sloppy though.
My guess is my hard drive held down the prtscn button enough to amass 15GB of screenshots since they look like they’re taken seconds from each other and stopped after my HD filled up.
Maybe I got lucky and have an incompetent hacker.
How many of you actually disable root and password based login, change the default SSH port, and setup fail2ban?
I just don’t put SSH on the internet at all.
This is 100% the way to go. I spun up a new server for a public-facing site on my VPS and I wondered if I really needed fail2ban. Within ten minutes of setting it up it had already blocked four people.
Don’t open port 22 if you can help it. Use it on your local network and VPN in if you need to use it offsite.
Is fail2ban not enough?
There’s no reason to allow root login, it’s asking for trouble. Password based login is even worse. Changing the SSH port just makes it harder for the drive-by bots trying the whole IPv4 range
That is part of my bootstrap ansible playbook, which in addition to create user, setting key, etc., will definitely disable root and password login, enable max tries and setup f2b. I am not necessarily afraid of exposing ssh to the internet (it is a service designed for it), but I drastically reduce the risk this way. I am thinking of also changing port to simply get less logs.
You’ve been scrot’ed!
My scrots are getting out of hand 😳
Not sure if serious…
What service has been attacked?