Thus said Baruch Burstein on Wed, 26 Aug 2015 11:33:09 +0300: > When I try to clone the fossil repo from https://fossil-scm.org, I get > an error that the SSL certificate is for sqlite.org. I also get this > error when browsing to https://fossil-scm.org. Is this a configuration > error?
I get no such error when cloning: $ fossil clone https://www.fossil-scm.org/ fossil.fossil Round-trips: 5 Artifacts sent: 0 received: 31870 Clone done, sent: 1199 received: 22908868 ip: 67.18.92.124 Rebuilding repository meta-data... 100.0% complete... Extra delta compression... Vacuuming the database... project-id: CE59BB9F186226D80E49D1FA2DB29F935CCA0333 server-id: 49a5737111af89604bc3fe8e2906d3a4b491a5ee admin-user: amb (password is "eb6d00") Also, the certificate has alternative names on it: X509v3 Subject Alternative Name: DNS:sqlite.org, DNS:system.data.sqlite.org, DNS:www.fossil-scm.org, DNS:www.sqlite.org If you are getting an error using one of those names, perhaps your list of CAs is out of date, or doesn't recognize the signing authority? Andy -- TAI64 timestamp: 4000000055ddbfb5 _______________________________________________ fossil-dev mailing list fossil-dev@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev
