scruffy
Notorious Olive Counter
Has anyone else encountered this problem?
Apparently, Verisign has switched to new certificate scheme, as of a few months ago.
Verisign's explanation is here: http://www.verisign.com/support/advisories/page_029264.html
(yes, it's available as an https page as well, and if you go to that same page as https, the cert checks out.)
Now, when I go to my work's remote login site using OS X
https://securelogin.gov.ab.ca
I get a certificate error (I get no error with Windows). I'm pretty technical, and I can't even figure out how to get a copy of this new Verisign certificate, signed with a key that I already do trust, to import it into my X509Anchors keychain...
So my questions three:
- Can someone else using a fully up-to-date OS X check whether they get this error?
- Can someone else using a fully up-to-date OS other than Windows check for this error?
- Has anyone encountered this same warning about the Verisign Class 3 Server Certificate elsewhere on the web?
I see two possibilities
- Verisign just didn't bother to get anyone but Microsoft to include their new certificates - they just don't care about the rest of the world.
- If the site in question distributed a full certificate chain, then it could get back to something Macs trust, but they just haven't configured it to do so, because it was only tested from Windows.
Apparently, Verisign has switched to new certificate scheme, as of a few months ago.
Verisign's explanation is here: http://www.verisign.com/support/advisories/page_029264.html
(yes, it's available as an https page as well, and if you go to that same page as https, the cert checks out.)
Now, when I go to my work's remote login site using OS X
https://securelogin.gov.ab.ca
I get a certificate error (I get no error with Windows). I'm pretty technical, and I can't even figure out how to get a copy of this new Verisign certificate, signed with a key that I already do trust, to import it into my X509Anchors keychain...
So my questions three:
- Can someone else using a fully up-to-date OS X check whether they get this error?
- Can someone else using a fully up-to-date OS other than Windows check for this error?
- Has anyone encountered this same warning about the Verisign Class 3 Server Certificate elsewhere on the web?
I see two possibilities
- Verisign just didn't bother to get anyone but Microsoft to include their new certificates - they just don't care about the rest of the world.
- If the site in question distributed a full certificate chain, then it could get back to something Macs trust, but they just haven't configured it to do so, because it was only tested from Windows.