View Single Post
Old 07-10-2019, 09:07 AM   #225
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,954
Karma: 6361444
Join Date: Nov 2009
Device: many
I will look into this. My guess is this has to deal with missing certificates. Older Macs had OpenSSL-1.0 installed and its default older certificates. Newer Macs do not have easy access to openssl. So I compile and statically link openssl into Python 3.7. I can not recreate this bug on my machine as I have full Openssl 1.1.1. I will look into the best way to handle this for newer machines that no longer have access to native apple OpenSSL installations.

Kevin

Quote:
Originally Posted by odamizu View Post
I'm behind on this plugin and installed the latest version today (v0.4.1.4).

On first run, I was startled to get a python error — something about SSL certificate verify failed. See screenshot.

The plugin then proceeded to run successfully, and it continues to run fine thereafter. The error occurs only on first run.

I suspect this has something to do with my Mac, which is running macOS 10.13.6.

Is this something I should be concerned about? Is there something I should do? Should I go back to an earlier version of the plugin that does not trigger this error on first-run? Or is this safe to ignore?

Thank you!

Last edited by KevinH; 07-10-2019 at 09:52 AM.
KevinH is online now   Reply With Quote