odd svn message

Going to check something in I get this, which I've never seen before....is it is safe to just hit P and go on?

now what? svn commit config/i386/llvm-i386.cpp
Error validating server certificate for 'https://llvm.org:443':
  - The certificate is not issued by a trusted authority. Use the
    fingerprint to validate the certificate manually!
Certificate information:
  - Hostname: llvm.org
  - Valid: from Tue, 10 Jun 2008 03:01:09 GMT until Fri, 26 Jun 2009 03:42:38 GMT
  - Issuer: Certification Services Division, Thawte Consulting cc, Cape Town, Western Cape, ZA
  - Fingerprint: 41:64:18:d3:30:18:f1:34:f7:6b:fb:26:13:51:55:f7:5d:3e:08:b3
(R)eject, accept (t)emporarily or accept (p)ermanently? ^Csvn: Commit failed (details follow):

That's the right fingerprint; I checked it by going to
https://llvm.org with Firefox and looking at the certificate. So you
should be safe just ignoring the error.

Did you do something to your OS configuration recently that would
affect the certificate store?

-Eli

Going to check something in I get this, which I've never seen
before....is it is safe to just hit P and go on?

now what? svn commit config/i386/llvm-i386.cpp
Error validating server certificate for 'https://llvm.org:443':
- The certificate is not issued by a trusted authority. Use the
  fingerprint to validate the certificate manually!
Certificate information:
- Hostname: llvm.org
- Valid: from Tue, 10 Jun 2008 03:01:09 GMT until Fri, 26 Jun 2009
03:42:38 GMT
- Issuer: Certification Services Division, Thawte Consulting cc,
Cape Town, Western Cape, ZA
- Fingerprint: 41:64:18:d3:30:18:f1:34:f7:6b:fb:26:13:51:55:f7:5d:3e:
08:b3

That's the right fingerprint; I checked it by going to
https://llvm.org with Firefox and looking at the certificate. So you
should be safe just ignoring the error.

Thanks.

Did you do something to your OS configuration recently that would
affect the certificate store?

No.
I note that at the time I got this, it was not yet 03:00 GMT on the 10th.

Did you do something to your OS configuration recently that would
affect the certificate store?

No.
I note that at the time I got this, it was not yet 03:00 GMT on the
10th.

We are investigating if the certificate got updated by UIUC administrators since they manage the certificates.

-Tanya

We are investigating if the certificate got updated by UIUC administrators
since they manage the certificates.

The certificate was listed as valid from June 9, 2008 so I guess the old one
expired?

Gr.

Matthijs

Matthijs Kooijman wrote:

We are investigating if the certificate got updated by UIUC administrators
since they manage the certificates.
    

The certificate was listed as valid from June 9, 2008 so I guess the old one
expired?
  

I just got email from TSG (our IT department). They did, in fact, install a new certificate yesterday because the old one was expiring soon, and its fingerprint matches the one sent by Dale in his email (41:64:18:d3:30:18:f1:34:f7:6b:fb:26:13:51:55:f7:5d:3e:08:b3). Our certificates are issued by Thawte, so if Thawte is not one of your trusted CAs, you SSL software will give a warning about the certificate.

The validity date of the new certificate is:

Not Before: Jun 9 19:01:09 2008 GMT
Not After : Jun 25 19:42:38 2009 GMT

So, if you trust Thawte as a CA and your time is set correctly, the certificate should be working for you now.

If you continue to get error messages about the certificate, please email the list.

-- John T.