That wasn't a very nice thing to say to me. I was just trying to help. This site is in danger. Anyone with any tech knowledge knows that.
I didn't take your comments primarily to
emphasize that personal information is in danger from no SSL.
I mean, it is, in some ways. Hard to put a good spin on it. Without SSL (i.e.
https://) anyone using the same starbucks WIFI as you can see your FC password / cookie in cleartext. It doesn't matter if it's "secure wifi" WPA2 and such. Same is true for anyone administering an ISP between you and FC -- I jump 13 steps to FC according to traceroute.
I think
@Hackerman you're also suggesting that the site might simply have gone dark if someone's credit card payment for renewal of a domain, not in control of the admins, hadn't recently gone through. Is that true, or apocryphal?
And, if I understand you, you're also pointing out that, without regular updates that patch
known, published exploits against XenForo and its database backend, a script kiddie can take the site down. In their documentation about possible vulnerabilities, XenForo mentions SQL injection and the risk of remote code execution on our OWN machines.
Obviously, FC isn't the focus of a serious black hat.
It's not a good position to be in, if all that is accurate. Yes, I understand site administrators are not in a position to fix it without the reappearance of one person. Not trying to offend anyone. But we should look technology reality in the face.
I take issue with the statement that personal information is no more at risk than when you joined.
Yes, the theoretical risk was there. But there is so much more malware out there now, so many more people and bots vacuuming up cleartext credentials than just a few years ago, you can't seriously say the risk isn't worse today.
And the risk of a bad actor tying your credentials to your actual personal identity is magnitudes greater today, surely.
ADDED:
To respect the privacy concerns of contributors here, may I please suggest that the site administrators enable individuals to delete not only their account but all of their historical postings, or at least individual postings, made without appreciation of the state of site administration and potential vulnerabilities.