Michał Trojnara
Michał Trojnara
@olszomal I'm afraid `check_key_fork` crash may be a separate issue...
Please always confirm that the bug is still present in the master branch when reporting a bug against a release. This helps us understand whether you only want us to...
I don't think OpenSSL's engine API allows for loading engines into a statically linked executable. This is not specific to libp11. Please consider opening an issue on https://github.com/openssl/openssl/ instead. Make...
This comment describes a very special theoretical scenario where your statically linked application exposes all the OpenSSL symbols that are needed by your engine. I don't think your application does...
Good news: `rk_sign_tool` appears to use OpenSSL 3.0.2 and export its symbols. It could work with our pkcs11 engine compiled against OpenSSL 3.0.2. ``` ⚡ strings rk_sign_tool | grep -A...
> I don't feel comfortable around autotools enough to force `libp11` to not link `libcrypto`, but I'll try looking up some clever method anyways I guess the dynamic loader should...
Yes, the application and the engine must use the same library. Compiling them against the same version is the essential first step, but then they need to be linked to...
I don't think there is anything else we can do to help with this issue.
This fairly trivial PR is required to build the code with recent releases of Arduino IDE. Please consider merging it.
How do you intend to use a static OpenSSL engine?