Ugh. Lame Update
10 years ago
General
It's nearly one in the morning, and I haven't slept for an entire day. As soon as I finish this journal entry, I'm going to get some sleep. So you may be wondering, "Why haven't you been sleeping?" The short answer is: I've been fighting with my webhost who didn't tell me my website was hit with a massive XSS injection, which corrupted a lot of my personal and professional files, including backups. Apparently I forgot to update one of the CMS on my server to the latest version, therefore I'm fiscally responsible for all the damage done even though they were aware my site was being attacked (at the time) and didn't tell me a goddamn thing. So $200+ later, site has been restored. Somewhat good as new. Spent all day and night fighting with technical support to dispute the charge. They compromised and gave me a discount. Now I'm low on money for the next few weeks and I'm concerned about it.
If my family was financially better off, I wouldn't be so stressed out about money right now. But my webhost and I are good now, and that's what matters in the interim. This is why I'm a few days behind with the third chapter of "Baby Business" and the commissions.
Over and out.
LS
If my family was financially better off, I wouldn't be so stressed out about money right now. But my webhost and I are good now, and that's what matters in the interim. This is why I'm a few days behind with the third chapter of "Baby Business" and the commissions.
Over and out.
LS
TheAnon
~theanon
...would someone accessing your site at the time of the attack be vulnerable as well?
FA+
