View Single Post
Old 10-09-2023, 06:29 PM   #1423
tomsem
Grand Sorcerer
tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.
 
Posts: 6,964
Karma: 27060153
Join Date: Apr 2009
Location: USA
Device: iPhone 15PM, Kindle Scribe, iPad mini 6, PocketBook InkPad Color 3
Quote:
Originally Posted by jhowell View Post
That is odd. This plugin includes a PDF handling library (pypdf) that can access the Python cryptographic libraries that are built into calibre. Those might be making use of openssl, but if so that is something that calibre handles, not the plugin.
I could not reproduce this on my MacBook, with the calibre environment there. DeACSM is not working there (I don't think I customized it there but it isn't even loading), but I did not see Tracebacks when operating the CLI.

I noticed that my iMac had a symlink, /usr/local/lib/libcrypto.dylib, that was not on my MacBook. I nuked it.

DeACSM is working again, and I'm not seeing the OSErrors operating the CLI.

My theory is that the symlink was somehow triggering some enhanced security of Sonoma, and left over from some previous install of OpenSSL when using such a symlink wasn't considered an issue.

But it's not my area of expertise, so all is well that ends well.

Last edited by tomsem; 10-09-2023 at 06:53 PM.
tomsem is offline   Reply With Quote