Closed Fernando-Cabral closed 7 months ago
Ah, I noticed that pyHanko's CI is currently also failing at the same Cython line in python-pkcs11, but I likely won't have time to debug until Sunday next week at the earliest...
Can you try accessing your pkcs11 module using another tool like pkcs11-tool to see if that works? Just to rule out problems with the module itself.
I suspect an upstream change in linked library versions or somesuch... pyHanko CI runs on ubuntu-latest
, which is at least in the same family as Debian. Did you recently upgrade things like openssl/libressl/... on your system? If so, I'd be curious to know what changed there.
My knee-jerk reaction was wrong. The issue with the CI is now resolved and turned out to be a softhsm2-specific issue (had to do with an interaction between the way I was provisioning the config and a test stack upgrade), so I'm converting this to a discussion.
Looking again at your issue with a fresh pair of eyes, I think it is what it says on the tin: the library you're trying to call is not a PKCS#11 module. libcrypto.so is the OpenSSL binary, which doesn't expose any PKCS#11 functionality. Are you sure you have the right library?
Describe the bug pyhank stopped working and started complaining about /lib/libcrypto.so.3: undefined symbol: C_GetFunctionList'
To Reproduce I have several versions of this library, so I tried one by one. They all failed with the same error message. Here is the code I used to test it:
Environment (please complete the following information):
Additional context
Other than the different path for each library version, the error message is the same, no matter which version I am using.
What should I try next?