a reply to:
DontTreadOnMe
Does this help?
Your connection may or may not be encrypted, e.g. http/https.
A connection must be encrypted to be a secure.
An encrypted connection may or may not be a secure depending on if the certificate chain from the end entity (
www.ats.com...) to the signing
authority also called the intermediate certificate, and finally to the root certificate. When all these curcumstances exist the secure connection is
"trusted".
There are dozens of factors which can make an otherwise trusted connection only secure or encrypted.
Expired certificate. LetsEncrypt certificates are free but they expire every 3 months. Personally i think certs should be renewed every 72 hours but
big businesses would go bonkers. Expired certs are arguably the most common reason for degraded security in the context to a connection.
Your clock is set incorrectly. This is usually not a problem with most modern web browsers because if you have an internet connection they dont need
your system clock to know wtf time it is. The browser probably knows better than your computer.
The certificate is revoked. # around and find out how quickly they can revoke a cert when you violate teems or openly support gun rights.
Your intermediate certificate is revoked. This has happened to starfield in recent times. If the signing authority fibds their private key for signing
gas been compromised then their intermediate certificate is revoked by the root authority and a new private key and intermediate cert is issued.
Your computer does not allow the combination of the protocol and cipher. Remember tls 1.3 vulnerabikuty? Probably not. I dont think you nerd out
like me, but thats okay. Basically if a service only negotiated to talk to your computer using that protocol, but your computer is locked down
properly, then the connection fails. Or perhaps they only offer strong ciphers and you dont have a security upsate installed to support them you
qould have problems.
Or perhaps the webserver is misconfigured. Or the cert does not match the host or other dns names stappled to it. Or there is something wrong with the
oscp stapling.
I could probably go on for hours about the reasons certificates fail. The point is to just understand there are 3 parties to a cert, and all must be
valid and agree to shake hands to be trusted.
I hope that makes sense cuz im a bit #ed up right now.
edit on 8-9-2021 by drewlander because: (no reason given)