 viperpa33sWhy Me?Premium
join:2002-12-20
Bradenton, FL | They should be called Veristink The company that I work for, the Verisign certificate for there website expired last night at around 7pm. After contacting the web hosting site IBM, and tracing the problem back to Verisign, was able to get the website up and running about 3 hours later.
The question is, who is responsible for this snafu? First we had the problem with Verisign rerouting people to there website if a person misspells a name. Now we have Verisign SSL certificates expiring causing many websites to go down and applications not working correctly. Seems to me that Verisign needs more oversight or there position over the internet taken away from them. |
|
| LoL I too ran disk cleanup, defrag, adaware, spybot, and made sure settings were ok. Doh! |
|
DA
join:2002-04-13
Greenville, SC | reply to viperpa33s
said by viperpa33s:
The question is, who is responsible for this snafu?
No offense but you are responsible for the snafu, the expiration of this certificate was announced when it was issued. I am no fan of Verisign but this was not their fault, the certificate expired when it was due to expire. |
|
 nixenRockin' the BoxenPremium
join:2002-10-04
Alexandria, VA | reply to viperpa33s
Here's a thought: whan you use SSL certificates, inspect the expiry dates for every certificate in the authority chain. Make special note of each epiry date and ensure that you have an action plan put in place BEFORE HAND.
OpenSSL is your friend in this. All you need to do, is once you've installed your certificate(s) is openssl s_client -port (SSLPORT) -host (SSLHOST). That will dump out the entire certificate chain from which you can parse out the various expiry dates.
-tom
--
"There are 10 types of people in the world... those who understand binary and those who don't."
"That's only 2 types of people, moron" |
|
