- Joined
- Apr 4, 2010
- Messages
- 8,873
Yeah so everyone has been going on about this Heartbleed bug...I'm just curious, is CFC vulnerable/was vulnerable? I would just like to know in case I need to change my password. 

Well, unless someone wants to read your pms....
Our SSL certificate was regenerated 2 days ago, so it might have been our hosts fixing the problem. I asked them, and will let you know.
I fully agree with that statement. Losing an account to a random stranger sounds quite bad as it would likely result in having to make a new account. Considering accounts have friends, post history and stuff like that, we really shouldn't rely on unencrypted transmissions for login details.It might not be a bad idea for CFC to add encryption of at least passwords, since there probably are a lot of people who use their CFC password for everything else, too, but I don't know how feasible that is with vBulletin.
I changed my password this morning as a precaution, just to be safe.
Heartbleed leaks data from memory meaning the action you can take to protect yourself on a compromised system is not to use it at all. That way your login info will stay on the disk and not in memory. Apart from that there is nothing the end user can do as Heartbleed is a server side bug.Changing a password before the fix won't do anything if a system is compromised. Password changes would have to be done after the fix to be 100% certain.
Changing a password before the fix won't do anything if a system is compromised. Password changes would have to be done after the fix to be 100% certain.
Isn't that a far worse problem than being hit by heartbleed? Rather than a breach of security, there is no security at allThe site does not use SSL.
Isn't that a far worse problem than being hit by heartbleed? Rather than a breach of security, there is no security at all![]()
The site does not use SSL.