Re: recent netbsd-7 certificate issue (unable to access google etc)

[David Brownlee <abs%absd.org@localhost>]

Time/date seem OK. I checked at the time, but now I just ran an 'ntpdc
-c peers' to show the exact offset and it looks like ntpd is just
timing out which is quite odd (time is certainly within a few
seconds).

Now I check my other netbsd-7 boxes are timing out on 'ntpdc -c peers'.

Bonus question - is anyone running ntpd on NetBSD-7 and does 'peers'
work for them?

On 12 February 2015 at 09:55, Chavdar Ivanov <ci4ic4%gmail.com@localhost> wrote:
> This happened to me on a Windows machine a few days ago when I had set the
> time to 2nd of May instead of 5th of February in the BIOS (it was MM/DD/YYYY
> fields, I entered DD/MM/YYYY, obviously). Receiving this message from Google
> was my first indication that the date was wrong.
>
> Chavdar Ivanov
>
> On Thu Feb 12 2015 at 9:28:22 AM David Brownlee <abs%absd.org@localhost> wrote:
>>
>> Is anyone seeing this?
>>
>> With recent netbsd-7/amd64 (201502092140Z downloaded from nyftp), and
>> pkgsrc rebuilt from source yesterday I'm unable to access google from
>> firefox, and konquerer gives a certificate error for the top certificate
>> in the chain (details below).
>>
>>
>> Common name: GeoTrust Global CA
>>
>> Organisation: GeoTrust Inc.
>>
>> Country: US:
>>
>> Issuer Orgaisation: Equifax
>>
>> Issuer Organizational Unit: Equifax Secure Certificate Authority
>>
>> Issuer Country: US:
>>
>> Trusted: NO, there were errors:
>> The certificate authority's certificate is invalid
>> The root certificate authority's certificate is not trusted for this
>> purpose
>>
>> Validity: 2002-05-21 04:00 to 2018-08-21 04:00
>>
>> Serial: 1227750
>>
>> MD5: 2e7db2a31d0e3da4b25f49b9542a2e1a
>>
>> SHA1: 7359755c6df9a0abc3060bce369564c8ec4542a3
>>
>>
>