Bug 17862 - mga6: /usr/bin/stunnel: symbol lookup error: undefined symbol: SSLv2_client_method
Summary: mga6: /usr/bin/stunnel: symbol lookup error: undefined symbol: SSLv2_client_m...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-02 03:39 CET by Bit Twister
Modified: 2016-03-02 18:58 CET (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Bit Twister 2016-03-02 03:39:14 CET 
Description of problem:

 stunnel[2643]: /usr/bin/stunnel: symbol lookup error: /usr/bin/stunnel: undefined symbol: SSLv2_client_method
 systemd[1]: stunnel.service: Control process exited, code=exited status=127

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. urpmi --download-all  --downloader wget --auto --auto-update
2. reboot
3. journalctl _SYSTEMD_UNIT=stunnel.service
Comment 1 Thomas Backlund 2016-03-02 08:55:45 CET 
Yeah, its a fallout of the upstream openssl security update/mitigation for CVE-2016-0800

Depends on: (none) => 17859
CC: (none) => tmb

Oden Eriksson 2016-03-02 09:10:52 CET

Depends on: 17859 => (none)

Comment 2 Thomas Backlund 2016-03-02 10:19:34 CET 
Please try again after you have installed openssl-1.0.2g-2.mga6
Comment 3 Bit Twister 2016-03-02 11:41:26 CET 
All better with the new release.

Resolution: (none) => FIXED
Status: NEW => RESOLVED

Comment 4 Bit Twister 2016-03-02 17:08:31 CET 
not so good with the band aid ripped of in openssl-1.0.2g-3.mga6.x86_64.rpm

Status: RESOLVED => REOPENED
Resolution: FIXED => (none)

Comment 5 Thomas Backlund 2016-03-02 17:18:07 CET 
yes, just wait, there are rebuilds in progress to cope with sslv2 removal
Comment 6 Bit Twister 2016-03-02 18:58:22 CET 
Latest stunnel release resolves the problem.

Status: REOPENED => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.