Insecure links

Page may contain affiliate links. Please see terms for details.
D

Deleted member 1258

Guest
I came across this a couple of years ago, but I can't remember what browser I was using or the cure for it. At the moment I'm not having trouble with links on phone tablet or desktop.
 

shirokazan

Veteran
Not an expert but I think this is a downside of Google's mission to switch the web from HTTP tp HTTPS.

I'm running Chrome at the moment and it is happening a lot to me - not just this forum.

Agree with SpokeyDokey. Google and others are driving a move to HTTPS which is resulting in the "insecure" messages. Here's Mozilla (the organisation behind FireFox) announcing their intention about 3 years. https://blog.mozilla.org/security/2015/04/30/deprecating-non-secure-http/
 

swee'pea99

Legendary Member
Recently I've been getting these when I click on links in messages:

upload_2018-11-25_13-30-29.png


Is it just me, or is summat up?
 
I've seen it a couple of times too, but it comes and goes. Mods ticked the 'discourage' box?
 
Generally warnings like that are a big no-no (suggesting that either the site you're visiting or your internet connection has been compromised) but in this case when you click an outgoing link on cyclechat it uses a redirect service - and the address CC uses for outgoing links "go.cyclechat.net" doesn't match the certificate of the redirect service and so your browser says "I've got a bad feeling about this"

In this instance it's not particularly risky. You can get around it by adding a security exception in your browser for go.cyclechat.net - though I would strongly advise against using security exceptions in general.
 

Shaun

Founder
Moderator
There are a couple of things going on:
  1. The fix for the wrongly redirected Amazon links turned out to be a much deeper problem than I'd originally anticipated and involved making some server and DNS changes; and because we use HTTP Strict Transport Security (HSTS) on the CC server the prior links to go.cyclechat.net are cached in everyone's browser for a long period and won't work again until they've expired (or been removed and replaced). Removal of HSTS domain settings in browsers is not easy so I've temporarily replaced go.cyclechat.net with a skimlinks link. Once the HSTS caching period has expired I'll reinstate the branded CC redirect.

  2. Google (and now other browser makers) have deprecated Chrome’s trust in the Symantec certificate authority (including Symantec-owned brands like Thawte, VeriSign, Equifax, GeoTrust, and RapidSSL). They announced their intention to do this in March - https://security.googleblog.com/2018/03/distrust-of-symantec-pki-immediate.html - but many site owners have either missed or ignored it and are now showing errors when visited using a browser with deprecated trust. Those site owners need to update their SSL certificates. CC uses a trusted certificate and is not affected by this.
Cheers,
Shaun
 

Similar threads

Top Bottom