2011/10/6 Jiri Navratil <[email protected]> > I'm back to port 443. I have to accept "Unknown SSL certificate". Sync is > working. Is Fingerprint all right? Accept always not save me before the same > questions. I have to find, how to avoid this "WARNING: Certificate doesn't > match the saved certificate for this host!" probably. > > Thank you, > Jiri > > fossil sync > Server: https://[email protected]/fossil > Bytes Cards Artifacts Deltas > Sent: 3132 66 0 0 > waiting for server... > Unknown SSL certificate: > > organizationName = sqlite.org > organizationalUnitName = Domain Control Validated > commonName = sqlite.org >
That's a UCC - a Unified Communications Certificate - which should be also valid for fossil-scm.org (and sqlite.com, and two other domains, all hosted off of the same web-server.) Do we need to do something to the Fossil SSL implementation so that it can accept a UCC? > > Issued By: > > countryName = US > stateOrProvinceName = Arizona > localityName = Scottsdale > organizationName = GoDaddy.com, Inc. > organizationalUnitName = http://certificates.godaddy.com/repository > commonName = Go Daddy Secure Certification Authority > serialNumber = 07969287 > > SHA1 Fingerprint: > > 90 a0 0e e6 73 65 65 85 38 81 94 1f 6a 22 6c f7 80 d1 ee 0b > > WARNING: Certificate doesn't match the saved certificate for this host! > Either: > * verify the certificate is correct using the SHA1 fingerprint above > * use the global ssl-ca-location setting to specify your CA root > certificates list > > If you are not expecting this message, answer no and contact your server > administrator. > > Accept certificate [a=always/y/N]? a > Received: 8371 132 0 0 > Total network traffic: 1917 bytes sent, 3612 bytes received > > -- > Jiri Navratil > > 6. 10. 2011 v 4:06, Richard Hipp: > > > > 2011/10/5 Jiří Navrátil <[email protected]> > >> Thank you very much. >> >> Based on your input, I used fossil remote-url to switch from port 443 to >> 80. Now I can sync. >> >> I will go back to port 443, when signed certificate will be available. I >> will report then result then. >> > > Please try it now and let me know how it goes. > > > >> >> Thank you, >> Jiri >> >> -- >> Jiri Navratil >> >> 4. 10. 2011 v 20:24, Konstantin Khomoutov: >> >> > On Tue, 4 Oct 2011 19:46:57 +0200 >> > Jiří Navrátil <[email protected]> wrote: >> > >> >> I'm getting this output: >> >> >> >> openssl s_client -host www.fossil-scm.org -port 443 >> >> CONNECTED(00000004) >> >> write:errno=54 >> >> >> >> not sure, which header file is applicable for me on OpenBSD >> > [...] >> > >> > I managed to find [1] which states that on your system 54 means >> > ECONNRESET, so you're facing the same issue I do. >> > >> > 1. http://fxr.watson.org/fxr/source/sys/errno.h?v=OPENBSD >> >> _______________________________________________ >> fossil-users mailing list >> [email protected] >> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >> > > > > -- > D. Richard Hipp > [email protected] > _______________________________________________ > fossil-users mailing list > [email protected] > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > > > > _______________________________________________ > fossil-users mailing list > [email protected] > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > > -- D. Richard Hipp [email protected]
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
