Somewhere thereabouts of last Tuesday night, our server got hacked. Right now the current estimate is via some kind of SSH exploit (we were running 3.8, latest stable is 4.3). It also appears there might have been some sort of Cacti exploit. Either way, as soon as we discovered it, the machine was shut down without ceremony. It’s taken this long to get it back up and running due to time restraints, but it’s all better now.
Back to your regularly scheduled poop and vagina jokes!
(And necrophilia! Don’t forget necrophilia! - ACW)
(And you can watch a movie about what happened, here. - ACW)
That was the funniest movie I’ve seen in forever. Well except for MI:3.
That movie was very acid trippy, man!
Glad you’re back up and running… or at least blogging!
I have no idea what SSH or Cacti exploit is, but it’s good to have you back.
well i for one was a little worried.
i feel better knowing it was just that you became an elf on a space cruise.
well i for one was a little worried.
i feel better knowing it was just that you became an elf on a space cruise.
and at burning man.
*movie-based-rofl* - welcome back!
i’m sorry i double posted.
please forgive me.
It’s about damned time you got back!
Seriously, sorry to hear about it and hope you’re back up and running minus the dipshits.
I’ve been out of the loop for a while, but was over taken with anxiety when I tried to visit you yesterday and you weren’t there.
Glad to have you back.
Welcome back! I think it’s time to invest in a new turkey… I mean, webmaster. ;-)
Apparently, someone’s l33t skilz are not nearly as good as the l33t haXX0r who hacked away. ;-)
Are you hosting this yourself, or did your host blow it?
SNMP on an exposed server? Joo gots zee balls my freend :P
Sorry. Sometimes I just have to be that guy. Welcome back.
It’s my own damn fault. For the record, SNMP wasn’t exposed on the server, it was accessible only to localhost. I’m still not sure how the hole was opened on Cacti, but it was a reasonably recent release of it. Also, from what I can tell, I got hit with some sort of undocumented exploit in combination with Linux.RST.B. My real mistake was allowing root login via SSH, which has now been rectified (along with a number of other not-so-best practices).
I am glad that you are back. I thought it might have been something more sinister.
dude..
i have a 32% comprehension of this post.
i am now off to remedial hacking for a brush up… i shall return a wiser man thanks to your pointing this out.
gracias.
and bring on the dead fucking jokes.. me likey
I am glad to see you back up and running. I could almost understand some of those words.
thank balls you’re back, i was thinking no one loved me and had blocked me and then my emo feeling got like, hurt, like.. *sniff*
Um. . .yeah. That was my bad.
I have SO missed you! I thought perhaps I had done something wrong (because generally, it’s my fault that anything goes wrong) and wasn’t able to come here anymore! I was upset! :) I hope it all works out for you now, and that you never, ever leave us again.
Thank you for your comment over at Off the Pace…my official count was 8 Coronas, 6 Miller Lites, and one vodka and tonic. I don’t know which one of those you want to put your name on!
Yay! I came back from a looonnngg break…and thought you had left the blogosphere! I was so bummed. But now I wanna do a dance…I’m thinking River Dance will do in this situation. With zombies, of course.
Thanks for the very informative movie. Without it I would never have understood what happened to your blog. Well, I still don’t understand, but I had a good laugh.
Good to “see” you again.