insaniak wrote:Most forums don't use SSL, as there's really no need for it. A forum isn't like a webstore, where you're transitting a bunch of personal information.
Also, (as I understand it) because it slows everything down, and flags security errors for anything linked from off-site.
It's true that on a forum you're not usually transmitting a lot of personal information, but forums do transmit one very important thing: a username and password combination. Because people have a big tendency to reuse credentials, this means any one forum leaking a password could be endangering a person's credentials for a huge number of sites. It's an unfortunate consequence of human behavior. Speed has not been a realistic obstacle to SSL/
TLS adoption in a very long time, but mixed-content warnings in the case of a forum that allows image embedding without rehosting the images can be a real headache.
legoburner wrote:There used to be a lot of arguments against using SSL (with Insaniak pointing out two of the big ones), as well as the endless server vulnerabilities popping up in openSSL for a while. There are still a few headaches that stop us implementing it (with mixed content warnings being a major one), but we'll probably turn it on at some point.
I've no doubt that mixed-content warnings are your biggest problem, since the boards allow inline display of external images. Firefox and Chrome both allow insecure images and will only log a warning in the
dev console, but I suppose you still have plenty of users on IE that will get big obnoxious warning interstitials. I'm happy you're at least considering it, and I hope you choose to do so relatively soon. I'm sure you keep your own council on how to go about these things but if you want I'm happy to discuss it with you further.