No OpenSSL 3.0 support
Bug #1954544 reported by
Thomas Ward
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xca (Debian) |
Fix Released
|
Unknown
|
|||
xca (Ubuntu) |
Fix Released
|
Critical
|
Unassigned |
Bug Description
It looks like XCA does not support OpenSSL 3.0 yet. As such, it cannot be included or built properly in Jammy.
I've submitted this as an upstream bug https:/
And have confirmed this issue happens with 2.4.0 as well (which is staged in Debian git for experimental, but is not going to be uploaded until OpenSSL 3 support is present.)
Changed in xca (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → Critical |
description: | updated |
Changed in xca (Debian): | |
status: | Unknown → Confirmed |
Changed in xca (Debian): | |
status: | Confirmed → Fix Released |
To post a comment you must log in.
I'm an evil person so I poked and prodded upstream to make sure they address this. OpenSSL 3.0 compat is in a branch here - https:/ /github. com/chris2511/ xca/compare/ xca-240- ossl3 - which succeeded passing the build tests in my 'junk drawer' PPA which is used for build tests on all archs with proposed enabled (https:/ /launchpad. net/~teward/ +archive/ ubuntu/ junk-drawer/ +packages).
There was no FTBFS and I have committed a patch containing the upstream branch changes to the Debian Salsa, and will be uploading that to Mentors shortly for them to include there in Unstable (it's seemingly reverse-compatible with teh older OpenSSL as well in unstable); once this is there I'll sync it down to Ubuntu and we'll see if it succeeds in Jammy like it does in the PPA.