Verisign Certificate Expiration Causes Multiple Problems
We had to do a little sleuthing today. Many readers wrote in with problems that turned out to be related. A certificate which Verisign used for signing SSL certificates has expired. When applications which depend on that certificate try to make an SSL connection, they fail and try to access crl.verisign.com, the certificate revocation list server. This has effectively DOS'ed that site, and Verisign has now updated the DNS record for that address to include several non-routable addresses, reducing the load on their servers. Some applications affected include older Internet Explorer browsers, Java, and Norton Antivirus (which may manifest itself as Microsoft Word being very slow to start). Hope this helps a few people, and if you have other apps with problems, please post about them below.
(which may manifest itself as Microsoft Word being very slow to start)
But.. I thought this SSL certificate expired just today..
Trolling is a art,
In an effort to have us forget about SiteFinder, they're going for an even bigger fuck-up.
Nice try, guys... now turn the CRL server back on.
... ... ...
HUH!?!
And I thought I was a geek...
What the hell does that mean, what does it do, and who do we sue for the class action lawsuit?
"Life's funny sometimes." "And sometimes it isn't." --Cat's Cradle
Well, it's good to know that not only crackers or script kiddies are good at taking down Verisign's services, that their own staff is good at it too.
Do not look into laser with remaining eye.
Heh.
The Army reading list
Well thank answers a lot of questions.. My M$ Word has been working terribly, however I thought that was status quo..
and if you have other apps with problems, please post about them below.
I can't get the DOS version of Duke Nukem to run in Windows XP. Is this at all somehow related? Is there a fix??
In other news, Microsoft, Red Hat, Oracle, Sun, and Apple had to do a little coding today.
Rumors abound that Arnold Schwarzenegger had to do a little governing today, but these allegations remain unconfirmed at this time. More at eleven.
Obliteracy: Words with explosions
sPh
route the traffic to some "SiteFinder service"?
Error: Id10t detected
> ...when you're about to enter a credit card number
> online it's assuring to see that the SSL cert is
> signed by a real organization...
Unfortunately, we usually have to settle for Verisign instead.
Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
...if you have other apps with problems, please post about them below.
Well, now that you mention it, my mother hasn't been able to print for a week, my uncle's PC keeps running checkdisk on startup, and I'm having trouble compiling kernel 2.6.0.
Oh yeah, and Unreal 2k3 has crappy frame rates on the 'Antalus' level, but maybe thats just my old ti4200 card.
Um. I think that's it for now. So when are you going to help me with these?
I'd rather be a conservative nutjob than a liberal with no nuts and no job.
There's actually a good reason for that -- self-signed certs don't protect you from DNS spoofing, which is ridiclously easy to do.
There is a way to install your home-brew cert into IE and Netscape/Mozilla. This works well for internal users.
Unless you have a P75, I don't see what you are talking about. MSWord has always started in less that 3 seconds on my system (PIII 700) and I can tell you that sometimes it is terribly bloated (My system, not Word).
Wait, did I just admit running Windows on slashdot? Bye bye Karma.
Write boring code, not shiny code!
One fix up to this:
Lesson: if the certificate expired yesterday, remove IIS and then reboot the thing.
HTH. HAND.
Soko
"Depression is merely anger without enthusiasm." - Anonymous
I hear that to get it to work with XP you need to upgrade to Duke Nukem Forever.
*ducks*
I think it beats another new "helpful" feature like "CRL Finder."
Or, in the case of MS:
Lesson: If __________________, reboot the thing.
$0.02 (CDN)
Hey, What did I do????
signed,
l33t_d00d@hotmail.com
- Not fuck up,
- Not fuck me over
But don't let it go to your head, l33t_d00d, that says more about them than you.the preceding comment is my own and in no way reflects the opinion of the Joint Chiefs of Staff
Well, after all, I should not be surprised to hear that, after the wildcard affair. They are definitely the masters for messing their DNS...
Wouldn't have been so bad if it was just my company, but folks from other companies, friends of friends, political buddies of friends of friends...
P.S. That was a joke....
Ummm, no it wasn't. You may *think* it was a joke, but trust me it wasn't.