-
Notifications
You must be signed in to change notification settings - Fork 170
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Segmentation fault: 11 under python included paramiko. OpenSSL 1.1.1k #336
Comments
It looks like the problem is not in the engine but in the openssl when registering ciphers. |
Encryption and signature by gost works fine from the command line. |
Are you able to get a more detailed stack trace? |
|
The only idea I currently have is that you somehow load the gost engine twice, once via the configuration file and the 2nd one from somehow else. I believe it may cause some harm. |
Those are two different openssl. Exactly why the locking call crashes, I don't know. Probably because it's not properly initialised in |
Yup, that's it. There's a global engine lock, which is initialized as part of initialization, and assumed to be initialized by However, even if that crash was fixed per se, the problem remains the same, gost is linked with a different openssl library than the one that called it, and that simply doesn't work. |
Hi.
I am facing a strange problem when using dynamic link libraries (gost.dylib)
MacOS BigSur 11.4
Installed OpenSSL 1.1.1k
and extension engine gost-1.1.dylib
From the command line, everything works fine - both encryption and signature.
The problem occurs in python when the paramiko library is included:
Gives an error message:
Fragment of the crash log:
Python debug (last lines):
The text was updated successfully, but these errors were encountered: