Are old cross-signed certs causing "iPXE cross-signing CA has expired" errors?
|
2016-09-07, 20:30
Post: #1
|
|||
|
|||
Are old cross-signed certs causing "iPXE cross-signing CA has expired" errors?
Are any certs still being served from http://ca.ipxe.org/auto signed by the cross-signing cert that expired in Feb 2016?
I see that http://ca.ipxe.org/cross-ca.crt is up to date. However, when running an https download from google cloud storage, ipxe reports that "iPXE cross-signing CA" has expired. Adding a new debug log line to crypto/x509.c I see that iPXE is using a cross-signing certificate that is valid "not after" 1456479729 (2016-02-26T09:42:09). See a screen shot here: https://storage.googleapis.com/dash-test...-error.png (I could not upload an attachment for this post) These are the two HTTP get requests from iPXE for the cross-signed certs (I believe). Code: GET /auto/5df65e6d.der?subject=ME4xCzAJBgNVBAYTAlVTMRAwDgYDVQQKEwdFcXVpZmF4MS0wKwYDVQQLEyRFcXVpZmF4IFNlY3VyZSBDZXJ0aWZpY2F0ZSBBdXRob3JpdHk= HTTP/1.1 And, I see that some *.der files have older timestamps than 31-Aug-2016: http://ca.ipxe.org/auto/ -- one in particular: 5df65e6d.der has an mtime of 01-Nov-2014. Unfortunately, I'm not able to inspect these .der files; openssl reports: Code: $ openssl x509 -inform der -in ~/Downloads/5df65e6d.der -out certificate.pem Is this an issue with out-of-date certs? Will it be fixed? Is there a repository or location for the scripts used to generate the auto/*.der files for self-hosting cross-signed certificate files? Commands used to build and test. Code: $ make EMBED=embed.ipxe bin/ipxe.iso DEBUG=x509,validator |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 1 Guest(s)