I recently upgraded my Apple devices to iOS 12.2 and now getting this warning in the url window. I do not know if this is in regard to the SSL Certificate already mentioned. First time I have seen it. I always wait a couple weeks before upgrading to check for bugs.
-------------- "You do not laugh when you look at the mountains, or when you look at the sea." Lafcadio Hearn
0
-------------- "You do not laugh when you look at the mountains, or when you look at the sea." Lafcadio Hearn
There is probably a setting to turn it off or tone down the warning message. I still haven't seen a compelling reason why sites like this need SSL encryption so not a priority to add it anytime soon.
The plan is to migrate the forum to new software in 2019 which is much higher priority from a security standpoint. Even if we implemented https right now there would still be warning messages due to mixed content (embedded http images). The newer software will play nicer in that regard.
The mixed content problem can be easily fixed with a simple query or dump, search and replace, and reload. If you will be upgrading the board software it will be a worthwhile goal to implement the ssl certificate at the same time. Depending on your host, the free Lets Encrypt certs can be a good option.
-------------- that elitist from silverdale wanted to tell me that all carnes are bad--Studebaker Hoch
0
-------------- that elitist from silverdale wanted to tell me that all carnes are bad--Studebaker Hoch
The mixed content problem can be easily fixed with a simple query or dump, search and replace, and reload. If you will be upgrading the board software it will be a worthwhile goal to implement the ssl certificate at the same time. Depending on your host, the free Lets Encrypt certs can be a good option.
The majority of thumbnails (roughly a half million) are hosted on another domain without SSL. It isn't practical to pipe the thumbnails (would significantly impact page loads for TRs with lots of images). The plan is to get the forum and images on the same domain when we upgrade the software and add SSL at that time. We could implement SSL for both domains now, but it's a non-trivial effort with trivial benefits (IMHO) so focusing on upgrading to more secure software to better secure the site first.
At home https doesn't do much. However when traveling aboard using a public WiFi I won't login to a website unless it has a https prefix due to cyber interceptions. There are other benefits including search engine optimization boosts. If NWHikers did not have a login it wouldn't matter much.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
Disclosure: As an Amazon Associate we earn from qualifying purchases when you use our link(s).
