Engine crashes when loading the configuration more than once
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openssl (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Undecided
|
Unassigned | ||
Hirsute |
Fix Released
|
Undecided
|
Unassigned | ||
Impish |
Fix Released
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
* Engine crashes when loading the configuration more than once
* Upstream started to avoid loading engines twice by using dynamic ids to track the loaded engines correctly
* OpenSSL 3
https:/
https:/
* OpenSSL 1.1.1 backports:
https:/
https:/
[Test Plan]
* https:/
The test a is run during the build as part of the upstream regression test suite, for the shared library build (as static build does not support engines), so you'll see one pass and one skip in the log.
[Where problems could occur]
* Separately we have started to fix userspace packages that needlessly load configuration files multiple times, which used to trigger this issue. The codepaths changed are with engine use, how they are loaded/
[Other Info]
* Previous bug reports about this issues are:
https:/
https:/
description: | updated |
description: | updated |
description: | updated |
Changed in openssl (Ubuntu Impish): | |
status: | New → In Progress |
Changed in openssl (Ubuntu Hirsute): | |
status: | New → In Progress |
description: | updated |
Changed in openssl (Ubuntu Focal): | |
status: | New → In Progress |
description: | updated |
Changed in openssl (Ubuntu Jammy): | |
status: | Confirmed → Fix Committed |
Status changed to 'Confirmed' because the bug affects multiple users.