Bug 17871 - mga6: stunnel Service [smtp-tls-wrapper] needs authentication to prevent MITM attacks
Summary: mga6: stunnel Service [smtp-tls-wrapper] needs authentication to prevent MI...
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: 6sta1
Depends on:
Blocks:
 
Reported: 2016-03-03 14:29 CET by Bit Twister
Modified: 2017-02-01 01:18 CET (History)
0 users

See Also:
Source RPM: stunnel-5.31-1.mga6.src.rpm
CVE:
Status comment:

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

Description Bit Twister 2016-03-03 14:29:23 CET 
Description of problem:

Mar 02 12:01:51 tb.home.test stunnel[2647]: LOG4[ui]: Service [smtp-tls-wrapper] needs authentication to prevent MITM attacks

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


How reproducible:


Steps to Reproduce:
1. journalctl | grep stunnel
Comment 1 David Walser 2016-03-04 20:16:12 CET 
That sounds to me like a local configuration issue and not a packaging bug.  If you're connecting to something via TLS, you need to be able to verify its certificate, which means you need to have a copy of it, or it needs to be signed by one of your configured CAs.

Keywords: (none) => NEEDINFO

Comment 2 Bit Twister 2016-03-04 22:49:44 CET 
(In reply to David Walser from comment #1)
> That sounds to me like a local configuration issue and not a packaging bug. 
> If you're connecting to something via TLS, you need to be able to verify its
> certificate, which means you need to have a copy of it, or it needs to be
> signed by one of your configured CAs.

I do not know. All I know is the message was/is not there on Mageia 3,4,5 releases.

Keywords: NEEDINFO => (none)

Bit Twister 2017-01-31 19:03:17 CET

Keywords: (none) => 6sta1

Comment 3 Bit Twister 2017-02-01 01:18:06 CET 
created my own /etc/stunnel/conf.d/xx__stunnel.conf.
No longer get error in journal.

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