| Summary: | stunnel service will not start without "fips = no" in conf file | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Bit Twister <bittwister2> |
| Component: | RPM Packages | Assignee: | QA Team <qa-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | bittwister2, cooker, dan, davidwhodgins, eeeemail, guillomovitch, mageia, sysadmin-bugs, tmb |
| Version: | 4 | Keywords: | Triaged, validated_update |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | advisory MGA4-64-OK | ||
| Source RPM: | stunnel-4.56-2.mga4.src.rpm | CVE: | |
| Status comment: | |||
|
Description
Bit Twister
2013-08-14 15:41:56 CEST
David Walser
2013-08-15 04:10:52 CEST
CC:
(none) =>
guillomovitch, mageia
Manuel Hiebel
2013-08-17 16:49:29 CEST
Keywords:
(none) =>
Triaged
Bit Twister
2014-01-18 16:34:17 CET
CC:
(none) =>
junknospam
Johnny A. Solbu
2014-01-18 18:11:09 CET
CC:
(none) =>
cooker Thanks Bit Twister. Bug confirmed with an upgrade from m3 to m4 final. The workaround, of adding "fips = no" fixes the problem. CC:
(none) =>
davidwhodgins
Dave Hodgins
2014-02-01 07:09:07 CET
Version:
Cauldron =>
4 I just submitted stunnel-4.56-3.3.mga4 in updates_testing, with FIPS mode support disabled at build time. Verified workaround is not required in release 5.
Samuel Verschelde
2015-07-01 12:34:32 CEST
Summary:
4_a1: stunnel service will not start without "fips = no" in conf file =>
stunnel service will not start without "fips = no" in conf file (In reply to Guillaume Rousse from comment #3) > I just submitted stunnel-4.56-3.3.mga4 in updates_testing, with FIPS mode > support disabled at build time. Was that meant to be assigned to QA as an update? It looks like it never was. Indeed, it was an error of mine. Suggested advisory: The stunnel package (stunnel-4.56-2) shipped in Mageia 4 was build to use FIPS compliance mode by defaut, requesting a specific feature unavailable in the openssl package. As a consequence, this execution mode had to be explicitely disabled in configuration for stunnel to work. A new package release (stunnel-4.56-3.3), available in updates_testing, fixes this issue by explicitly disabling support for this non-working FIPS compliance mode. Status:
NEW =>
ASSIGNED Advisory committed to svn and validating the update. Keywords:
(none) =>
validated_update unvalidating as there is no stunnel-4.56-3.3 (actually no stunnel package at all) in 4 core updates_testing Keywords:
validated_update =>
(none)
Samuel Verschelde
2015-07-10 11:14:16 CEST
Whiteboard:
MGA4-64-OK advisory =>
advisory feedback $ rpm -qa|grep stunnel stunnel-4.56-3.3.mga4 It's not in my local repo now though, so it must have been removed. Guillaume, Any idea what's going on with stunnel? Guillaume ping I just submitted stunnel-4.56-3.3.mga4 again. I tested stunnel-4.56-3.3.mga4.i586 with popa3d, and it works once the fips=no line is completely removed from the popa3d config file. I'll fix that in Cauldron as it's not shipped in mga4 or mga5. I just realized I made a wrong assumption about the stunnel version in Cauldron, but I'll make sure popa3d is still working there separately. Any change to make to the advisory before I validate it again? http://svnweb.mageia.org/advisories/11000.adv?view=markup Whiteboard:
advisory feedback =>
advisory feedback MGA4-64-OK I fixed a couple of typos but it looks fine now.
Dave Hodgins
2015-08-06 17:58:16 CEST
Keywords:
(none) =>
validated_update An update for this issue has been pushed to Mageia Updates repository. http://advisories.mageia.org/MGAA-2015-0079.html Status:
ASSIGNED =>
RESOLVED |