On Jun 7, 2018, at 1:52 PM, Stephen Chrzanowski <pontia...@gmail.com> wrote: > > Its running Debian Lenny.
That OS is over 9 years old now. I’ve been known to run Linux boxes longer than that, but one of the several tradeoffs for that stability is that you must accept incompatibilities like this. Besides the CA database issue brought up above, there is another common cause for wget/curl complaints with HTTPS connections: the TLS/SSL and/or crypto library in use on the system is old enough that it doesn’t support any of the encryption protocols offered by the web server. Web servers are often configured specifically to refuse old and known-broken protocols, with the attendant hit to backwards compatibility. Do you really need something in the daily scrape that you wouldn’t get from a Fossil clone? There are a few things on sqlite.org that aren’t in the Fossil repo, but perhaps not as many as you’d guess. I ask because if you build a Fossil binary by hand, you can link it to an up-to-date version of OpenSSL, which may solve the certificate problem. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
