When I unload softhsm from anything which uses OpenSSL, I get a crash: Program received signal SIGSEGV, Segmentation fault. 0x00007ffff547e990 in ?? () (gdb) bt #0 0x00007ffff547e990 in ?? () #1 0x00007ffff6e0c312 in CRYPTO_THREADID_current (id=0x7fffffffd490) at cryptlib.c:493 #2 0x00007ffff6ec6468 in ERR_remove_thread_state (id=id@entry=0x0) at err.c:997 #3 0x0000000000419d42 in main (Argc=<optimized out>, Argv=<optimized out>) at openssl.c:437 This is https://github.com/opendnssec/SoftHSMv2/issues/239 Fixed in https://github.com/opendnssec/SoftHSMv2/commit/371686fb68ef
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.