stunnel4: runtime check on openssl too tight?
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
stunnel4 (Debian) |
Fix Released
|
Unknown
|
|||
stunnel4 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Imported from Debian bug http://
Package: stunnel4
Version: 3:5.63-1
Severity: serious
User: <email address hidden>
Usertags: flaky
The debci testsuite failed for all architectures after the recent
openssl upload
https:/
Am I right to assume as per
| logs/results.
| logs/results.
| logs/results.
…
| autopkgtest [04:07:41]: test upstream: -------
| upstream FAIL non-zero exit status 1
| autopkgtest [04:07:41]: test upstream: - - - - - - - - - - results - - - - - - - - - -
| autopkgtest [04:07:41]: @@@@@@@
| debian-python PASS
| upstream FAIL non-zero exit status 1
that the error is that it was compiled against one version (1.1.1n)
and then tested against another version (1.1.1o)?
stunnel4 -version reports:
| Compiled with OpenSSL 1.1.1n 15 Mar 2022
| Running with OpenSSL 1.1.1o 3 May 2022
and it is fine, the ABI is stable.
Sebastian
tags: | added: update-excuse |
tags: | removed: update-excuse |
Changed in stunnel4 (Debian): | |
importance: | Undecided → Unknown |
Changed in stunnel4 (Debian): | |
status: | New → Fix Released |
This bug was fixed in the package stunnel4 - 3:5.63-1ubuntu1
---------------
stunnel4 (3:5.63-1ubuntu1) kinetic; urgency=medium
* d/p/06- no-openssl- version- check-autopkgte st.patch: fix autopkgtests
when running against a new OpenSSL version, preventing having to rebuild
the package at each point release. Closes: #1010698; LP: #1972801
-- Simon Chopin <email address hidden> Thu, 30 Jun 2022 13:56:36 +0200