At any rate, I don't have much time left after that little adventure.
I spent a lot of time Saturday optimizing the site, and waiting on the computer/phone with my webhost, Hostgator.
They wanted to blame me/CathInfo rather than the attacker for some reason. They kept treating it as a normal "traffic overage" issue, and they have to protect the other accounts on the server, yadda yadda.
I understand the other accounts don't deserve to be affected. BUT -- why not re-enable CathInfo once the latest attacker IPs have been dealt with? Why cause CathInfo to be down for hours unnecessarily? The tech support man who dealt with the latest attack wave knew what he was doing. He knew it was dealt with -- and yet he didn't have the authority to re-enable the site. Sounds like I need to find a better webhost. By the way, my host is HOSTGATOR. I do not recommend them. If I had more time, I'd work on switching hosts.
But right now it's Sunday, and that means time to get ready to host Mass here again. Things need to be prepared and cleaned, and we have High Mass and potluck today (1st Sunday of the month), so there's some extra preparation there.