This is a discussion on Issue with verisign intermediate ca.. within the Linux Web Servers forums, part of the Web Server and Related Forums category; I've got this issue, close to identical; but with Netscape 7.2/Firefox 1.0.3 (current versions) instead ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
I've got this issue, close to identical; but with Netscape 7.2/Firefox
1.0.3 (current versions) instead of IE: http://www.issociate.de/board/post/4...t_problem.html Identically, I've installed the latest intermediate.crt, indicated its location in both ways outlined in that post in httpd.conf, and I get no issue/warning in IE on Windows (I can verify that it's being given the correct intermediate.crt, which expires in 2011); but I do get an invalid cert warning in each of the other browsers. In each case, the Class 3 Public Primary OCSP Responder is the closest thing I can find to what I ought to delete; but imposing this on customers logging isn't exactly convenient. Is there a way to overcome this without imposing this inconvenience on customers? |
|
|||
|
I would otherwise be writing instructions for customers that would
imitate this: https://knowledge.verisign.com/searc...jsp?id=vs27207 Idle curiosity inspires one to wonder why the latest version of each of these browsers installs with an expired one? I've confirmed I'm not the only one who gets the warning.. |