Status: Piecing together the system calls this malware makes.
The server will be wiped, naturally, but I actually enjoy the forensics side of this.
@joeo10 I'm more than a little suspicious of what this "code of conduct breech" was. Since no-one's spelling it out and most of the vitriol seems to be coming from the people forking the project, I'm inclined to think THEY are the problem.
I miss projects being about the code instead of the crusading bullshit.
And I do not care how unpopular that viewpoint is.
Nothing like getting a call in the AM saying, "I think we've been hacked".
Got it under control now, I think. The processes watching each other, and thus respawning when one is killed, have been isolated with kill -STOP.
Load averages have dropped from the mid 50s to 0.02.
Now to clear out the SysV init section so they don't respawn on reboot.
Running md5sums on everything. Will replace the diddled-with services. Already did that with the usual suspects (ps, who, top, etc)
I hate my life.
@matigo Yep. He learned the big difference between mixed marital arts and boxing. I'm glad they stopped it when they did because his legs and head movement were kaput after that last right Mayweather nailed him with. Also, his punches had nothing on them by that point. Mayweather could walk right through them.
Having him go another couple of rounds taking shots like that would have been bad news.
Mayweather - MacGregor went about like I thought it would. Just went two rounds longer than I had it going.
MacGregor has nothing to be ashamed of. He boxed a hell of a lot better than I thought he would.
Puttering through space and listening to a livestream of storm coverage. I have customers on that area. Rather concerned
@JeremyCherfas Mine is coming up in 15 hours and I am so looking forward to it.