When I last got this error, it's because my time program was off by a few
years, and therefore the cert was not inside it's trusted times, and therefore
the cert was seen as invalid.
--Sean
Somebody claiming to be bofh wrote:
I noticed something is different about the openbsd 4.5
Clocks are all good ;). First thing I enable was openntpd.
Unfortunately, I'm seeing the same behavior from firefox downloaded
from mozilla too, even on osx. A search for the invalid cert term
indicated that this is new behavior (stricter) on firefox-3 series.
It appears that if I want the old
I noticed something is different about the openbsd 4.5 mozilla-firefox
package vs say, kubuntu's build.
I set up paros (MITM proxy) with it's own cert (wildcard cert) signed
by my cacert.pem file. I added this root cert to the openbsd firefox.
I can go to https://mail.google.com without
3 matches
Mail list logo