[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#854876: marked as done (reportbug: SMTP and STARTTLS: SSLV3_ALERT_HANDSHAKE_FAILURE)

Your message dated Thu, 19 Nov 2020 20:59:24 +0100
with message-id <16f1f4d8-51a9-0fd6-0e39-4926078e0571@web.de>
and subject line Re: reportbug: SMTP and STARTTLS: SSLV3_ALERT_HANDSHAKE_FAILURE
has caused the Debian Bug report #854876,
regarding reportbug: SMTP and STARTTLS: SSLV3_ALERT_HANDSHAKE_FAILURE
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
854876: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854876
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: reportbug
Version: 7.1.4
Severity: important

Dear Maintainer,

Reportbug fails to talk to my smarthost in order to send mail with the
error message:

  SMTP send failure: [SSL: SSLV3_ALERT_HANDSHAKE_FAILURE] sslv3 alert
  handshake failure (_ssl.c:720).

Apparently reportbug doesn't support TLS configured with reasonable
ciphers. Relevant postfix config snippet:

  smtpd_tls_security_level = may
  # use server cipher ordering
  tls_preempt_cipherlist = yes
  # TLS only, no SSL
  smtpd_tls_protocols = !SSLv2, !SSLv3
  smtpd_tls_ciphers = high
  tls_high_cipherlist = HIGH:!aNULL:@STRENGTH

-- 
Regards,
Scott.

-- Package-specific info:
** Environment settings:
EDITOR="vi"
DEBEMAIL="scott@sl.id.au"
DEBFULLNAME="Scott Leggett"
INTERFACE="text"

** /home/scott/.reportbugrc:
reportbug_version "6.5.1"
mode standard
ui text
smtphost "mail.sl.id.au:587"
smtpuser "scott@sl.id.au"
smtptls

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing'), (50, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages reportbug depends on:
ii  apt                1.4~beta4
ii  python3-reportbug  7.1.4
pn  python3:any        <none>

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn  claws-mail                                 <none>
pn  debconf-utils                              <none>
pn  debsums                                    <none>
pn  dlocate                                    <none>
pn  emacs23-bin-common | emacs24-bin-common    <none>
ii  exim4-daemon-light [mail-transport-agent]  4.88-5
ii  file                                       1:5.29-3
ii  gir1.2-gtk-3.0                             3.22.7-2
ii  gir1.2-vte-2.91                            0.46.1-1
ii  gnupg                                      2.1.18-3
ii  python3-gi                                 3.22.0-2
ii  python3-gi-cairo                           3.22.0-2
pn  python3-gtkspellcheck                      <none>
pn  python3-urwid                              <none>
ii  xdg-utils                                  1.1.1-1

Versions of packages python3-reportbug depends on:
ii  apt                1.4~beta4
ii  file               1:5.29-3
ii  python3-debian     0.1.30
ii  python3-debianbts  2.6.1
ii  python3-requests   2.12.4-1
pn  python3:any        <none>

python3-reportbug suggests no packages.

-- no debconf information

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- 
On 12 Feb 2017 Scott Leggett wrote:


Apparently reportbug doesn't support TLS configured with reasonable
ciphers.
Reportbug does not directly implement any SSL/TLS support, but relies on python's smtplib for handling this during message transmission. Since this bug is also already some years old and may not be reproducible anymore, I'm closing it now.
If you are still seeing this problem with the latest reportbug, please file a new bug against python and mark it as affecting reportbug. Thanks!
--- End Message ---
Reply to: