| 2018-10-23 04:34:09 |
Moses Moore |
bug |
|
|
added bug |
| 2018-11-02 06:43:32 |
ԜаӀtеr Ⅼарсһуnѕkі |
sylpheed (Ubuntu): status |
New |
Triaged |
|
| 2019-09-13 07:47:54 |
vofka |
bug |
|
|
added subscriber vofka |
| 2019-09-25 14:37:59 |
vofka |
attachment added |
|
1-3.5.1-1ubuntu5.debdiff https://bugs.launchpad.net/ubuntu/+source/sylpheed/+bug/1799345/+attachment/5291160/+files/1-3.5.1-1ubuntu5.debdiff |
|
| 2019-09-25 16:28:07 |
Ubuntu Foundations Team Bug Bot |
tags |
amd64 apport-bug cosmic |
amd64 apport-bug cosmic patch |
|
| 2019-09-25 16:28:16 |
Ubuntu Foundations Team Bug Bot |
bug |
|
|
added subscriber Ubuntu Sponsors Team |
| 2019-09-25 16:37:09 |
Thomas Ward |
removed subscriber Ubuntu Sponsors Team |
|
|
|
| 2019-09-28 15:22:17 |
vofka |
description |
Problem appeared after upgrading from Ubuntu 18.04 to 18.10.
When starting Sylpheed, connecting to imap.gmail.com over SSL, I get a warning embedded in the SSL certificate: "Subject: /OU=No SNI provided; please fix your client./CN=invalid2.invalid "
May be related to this bug report about 'fetchmail' in redhat enterprise when it was still using TLSv1.2 instead of TLSv1.3:
https://bugzilla.redhat.com/show_bug.cgi?id=1611815
https://gitlab.com/fetchmail/fetchmail/commit/9b8b634312f169fab872f3580c2febe5af031615
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: sylpheed 3.5.1-1ubuntu3
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Oct 23 00:27:01 2018
InstallationDate: Installed on 2016-06-05 (869 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: sylpheed
UpgradeStatus: Upgraded to cosmic on 2018-10-21 (1 days ago)
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2018-03-20T22:16:27.108498 |
IMAP connection to imap.gmail.com over SSL returns self-signed certificate. Though you can still connect to imap.gmail.com using this certificate, it would be better to fix it to avoid this scary warning (self-signed certificate) and provide a smoother user experience.
Test Case
Install sylpheed. Start sylpheed. Create IMAP account for gmail.com in sylpheed (IMAP4 (Gmail)). Check for new email. You should get a warning complaining about self-signed certificate.
With fixed package, try the same. This time you should not get the warning.
Original Description
--------------------
Problem appeared after upgrading from Ubuntu 18.04 to 18.10.
When starting Sylpheed, connecting to imap.gmail.com over SSL, I get a warning embedded in the SSL certificate: "Subject: /OU=No SNI provided; please fix your client./CN=invalid2.invalid "
May be related to this bug report about 'fetchmail' in redhat enterprise when it was still using TLSv1.2 instead of TLSv1.3:
https://bugzilla.redhat.com/show_bug.cgi?id=1611815
https://gitlab.com/fetchmail/fetchmail/commit/9b8b634312f169fab872f3580c2febe5af031615
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: sylpheed 3.5.1-1ubuntu3
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Oct 23 00:27:01 2018
InstallationDate: Installed on 2016-06-05 (869 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: sylpheed
UpgradeStatus: Upgraded to cosmic on 2018-10-21 (1 days ago)
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2018-03-20T22:16:27.108498 |
|
| 2019-09-28 15:24:44 |
vofka |
tags |
amd64 apport-bug cosmic patch |
amd64 apport-bug bionic cosmic patch |
|
| 2019-09-28 15:27:12 |
vofka |
attachment added |
|
1-3.5.1-1ubuntu3.18.04.1.debdiff https://bugs.launchpad.net/ubuntu/+source/sylpheed/+bug/1799345/+attachment/5292251/+files/1-3.5.1-1ubuntu3.18.04.1.debdiff |
|
| 2019-10-04 15:51:52 |
vofka |
description |
IMAP connection to imap.gmail.com over SSL returns self-signed certificate. Though you can still connect to imap.gmail.com using this certificate, it would be better to fix it to avoid this scary warning (self-signed certificate) and provide a smoother user experience.
Test Case
Install sylpheed. Start sylpheed. Create IMAP account for gmail.com in sylpheed (IMAP4 (Gmail)). Check for new email. You should get a warning complaining about self-signed certificate.
With fixed package, try the same. This time you should not get the warning.
Original Description
--------------------
Problem appeared after upgrading from Ubuntu 18.04 to 18.10.
When starting Sylpheed, connecting to imap.gmail.com over SSL, I get a warning embedded in the SSL certificate: "Subject: /OU=No SNI provided; please fix your client./CN=invalid2.invalid "
May be related to this bug report about 'fetchmail' in redhat enterprise when it was still using TLSv1.2 instead of TLSv1.3:
https://bugzilla.redhat.com/show_bug.cgi?id=1611815
https://gitlab.com/fetchmail/fetchmail/commit/9b8b634312f169fab872f3580c2febe5af031615
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: sylpheed 3.5.1-1ubuntu3
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Oct 23 00:27:01 2018
InstallationDate: Installed on 2016-06-05 (869 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: sylpheed
UpgradeStatus: Upgraded to cosmic on 2018-10-21 (1 days ago)
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2018-03-20T22:16:27.108498 |
IMAP connection to imap.gmail.com over SSL returns self-signed certificate. Though you can still connect to imap.gmail.com using this certificate, it would be better to fix it to avoid this scary warning (self-signed certificate) and provide a smoother user experience.
Test Case
Create IMAP account for gmail.com in sylpheed. To do this, select "Create new account" from the "Configuration" in the main menu. "New account setup" window will appear. Select "IMAP4 (Gmail)" and follow instructions in that window. After setup is finished check for new email for newly created account. You should get a warning complaining about self-signed certificate.
With fixed package, try the same. This time you should not get the warning.
Original Description
--------------------
Problem appeared after upgrading from Ubuntu 18.04 to 18.10.
When starting Sylpheed, connecting to imap.gmail.com over SSL, I get a warning embedded in the SSL certificate: "Subject: /OU=No SNI provided; please fix your client./CN=invalid2.invalid "
May be related to this bug report about 'fetchmail' in redhat enterprise when it was still using TLSv1.2 instead of TLSv1.3:
https://bugzilla.redhat.com/show_bug.cgi?id=1611815
https://gitlab.com/fetchmail/fetchmail/commit/9b8b634312f169fab872f3580c2febe5af031615
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: sylpheed 3.5.1-1ubuntu3
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Oct 23 00:27:01 2018
InstallationDate: Installed on 2016-06-05 (869 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: sylpheed
UpgradeStatus: Upgraded to cosmic on 2018-10-21 (1 days ago)
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2018-03-20T22:16:27.108498 |
|
| 2019-10-04 15:55:37 |
vofka |
bug |
|
|
added subscriber Ubuntu Sponsors Team |
| 2019-10-08 20:28:48 |
Dan Streetman |
bug watch added |
|
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908063 |
|
| 2019-10-08 20:28:48 |
Dan Streetman |
bug task added |
|
sylpheed |
|
| 2019-10-08 20:28:57 |
Dan Streetman |
bug task deleted |
sylpheed |
|
|
| 2019-10-08 20:29:09 |
Dan Streetman |
bug task added |
|
sylpheed (Debian) |
|
| 2019-10-08 20:29:37 |
Dan Streetman |
nominated for series |
|
Ubuntu Bionic |
|
| 2019-10-08 20:29:37 |
Dan Streetman |
bug task added |
|
sylpheed (Ubuntu Bionic) |
|
| 2019-10-08 20:29:37 |
Dan Streetman |
nominated for series |
|
Ubuntu Eoan |
|
| 2019-10-08 20:29:37 |
Dan Streetman |
bug task added |
|
sylpheed (Ubuntu Eoan) |
|
| 2019-10-08 20:29:37 |
Dan Streetman |
nominated for series |
|
Ubuntu Disco |
|
| 2019-10-08 20:29:37 |
Dan Streetman |
bug task added |
|
sylpheed (Ubuntu Disco) |
|
| 2019-10-08 20:31:52 |
Dan Streetman |
description |
IMAP connection to imap.gmail.com over SSL returns self-signed certificate. Though you can still connect to imap.gmail.com using this certificate, it would be better to fix it to avoid this scary warning (self-signed certificate) and provide a smoother user experience.
Test Case
Create IMAP account for gmail.com in sylpheed. To do this, select "Create new account" from the "Configuration" in the main menu. "New account setup" window will appear. Select "IMAP4 (Gmail)" and follow instructions in that window. After setup is finished check for new email for newly created account. You should get a warning complaining about self-signed certificate.
With fixed package, try the same. This time you should not get the warning.
Original Description
--------------------
Problem appeared after upgrading from Ubuntu 18.04 to 18.10.
When starting Sylpheed, connecting to imap.gmail.com over SSL, I get a warning embedded in the SSL certificate: "Subject: /OU=No SNI provided; please fix your client./CN=invalid2.invalid "
May be related to this bug report about 'fetchmail' in redhat enterprise when it was still using TLSv1.2 instead of TLSv1.3:
https://bugzilla.redhat.com/show_bug.cgi?id=1611815
https://gitlab.com/fetchmail/fetchmail/commit/9b8b634312f169fab872f3580c2febe5af031615
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: sylpheed 3.5.1-1ubuntu3
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Oct 23 00:27:01 2018
InstallationDate: Installed on 2016-06-05 (869 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: sylpheed
UpgradeStatus: Upgraded to cosmic on 2018-10-21 (1 days ago)
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2018-03-20T22:16:27.108498 |
[impact]
IMAP connection to imap.gmail.com over SSL returns self-signed certificate. Though you can still connect to imap.gmail.com using this certificate, it would be better to fix it to avoid this scary warning (self-signed certificate) and provide a smoother user experience.
[Test Case]
Create IMAP account for gmail.com in sylpheed. To do this, select "Create new account" from the "Configuration" in the main menu. "New account setup" window will appear. Select "IMAP4 (Gmail)" and follow instructions in that window. After setup is finished check for new email for newly created account. You should get a warning complaining about self-signed certificate.
With fixed package, try the same. This time you should not get the warning.
[regression potential]
low, as this only sets SNI, however any regression would likely result in SSL connection failures.
[other info]
for Bionic, this is almost certainly a regression caused by the openssl upgrade to 1.1.
---
Original Description
--------------------
Problem appeared after upgrading from Ubuntu 18.04 to 18.10.
When starting Sylpheed, connecting to imap.gmail.com over SSL, I get a warning embedded in the SSL certificate: "Subject: /OU=No SNI provided; please fix your client./CN=invalid2.invalid "
May be related to this bug report about 'fetchmail' in redhat enterprise when it was still using TLSv1.2 instead of TLSv1.3:
https://bugzilla.redhat.com/show_bug.cgi?id=1611815
https://gitlab.com/fetchmail/fetchmail/commit/9b8b634312f169fab872f3580c2febe5af031615
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: sylpheed 3.5.1-1ubuntu3
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Oct 23 00:27:01 2018
InstallationDate: Installed on 2016-06-05 (869 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: sylpheed
UpgradeStatus: Upgraded to cosmic on 2018-10-21 (1 days ago)
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2018-03-20T22:16:27.108498 |
|
| 2019-10-08 20:32:04 |
Dan Streetman |
tags |
amd64 apport-bug bionic cosmic patch |
amd64 apport-bug bionic cosmic patch regression-update |
|
| 2019-10-08 20:33:40 |
Dan Streetman |
description |
[impact]
IMAP connection to imap.gmail.com over SSL returns self-signed certificate. Though you can still connect to imap.gmail.com using this certificate, it would be better to fix it to avoid this scary warning (self-signed certificate) and provide a smoother user experience.
[Test Case]
Create IMAP account for gmail.com in sylpheed. To do this, select "Create new account" from the "Configuration" in the main menu. "New account setup" window will appear. Select "IMAP4 (Gmail)" and follow instructions in that window. After setup is finished check for new email for newly created account. You should get a warning complaining about self-signed certificate.
With fixed package, try the same. This time you should not get the warning.
[regression potential]
low, as this only sets SNI, however any regression would likely result in SSL connection failures.
[other info]
for Bionic, this is almost certainly a regression caused by the openssl upgrade to 1.1.
---
Original Description
--------------------
Problem appeared after upgrading from Ubuntu 18.04 to 18.10.
When starting Sylpheed, connecting to imap.gmail.com over SSL, I get a warning embedded in the SSL certificate: "Subject: /OU=No SNI provided; please fix your client./CN=invalid2.invalid "
May be related to this bug report about 'fetchmail' in redhat enterprise when it was still using TLSv1.2 instead of TLSv1.3:
https://bugzilla.redhat.com/show_bug.cgi?id=1611815
https://gitlab.com/fetchmail/fetchmail/commit/9b8b634312f169fab872f3580c2febe5af031615
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: sylpheed 3.5.1-1ubuntu3
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Oct 23 00:27:01 2018
InstallationDate: Installed on 2016-06-05 (869 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: sylpheed
UpgradeStatus: Upgraded to cosmic on 2018-10-21 (1 days ago)
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2018-03-20T22:16:27.108498 |
[impact]
IMAP connection to imap.gmail.com over SSL returns self-signed certificate. Though you can still connect to imap.gmail.com using this certificate, it would be better to fix it to avoid this scary warning (self-signed certificate) and provide a smoother user experience.
[Test Case]
Create IMAP account for gmail.com in sylpheed. To do this, select "Create new account" from the "Configuration" in the main menu. "New account setup" window will appear. Select "IMAP4 (Gmail)" and follow instructions in that window. After setup is finished check for new email for newly created account. You should get a warning complaining about self-signed certificate.
With fixed package, try the same. This time you should not get the warning.
[regression potential]
low, as this only sets SNI, however any regression would likely result in SSL connection failures.
[other info]
for Bionic, this is almost certainly a regression caused by the openssl upgrade to 1.1.
for Disco and Eoan, this functionality likely has never worked, as we haven't synced this package from Debian since Bionic.
Debian does have this patch as noted in the Affects section.
---
Original Description
--------------------
Problem appeared after upgrading from Ubuntu 18.04 to 18.10.
When starting Sylpheed, connecting to imap.gmail.com over SSL, I get a warning embedded in the SSL certificate: "Subject: /OU=No SNI provided; please fix your client./CN=invalid2.invalid "
May be related to this bug report about 'fetchmail' in redhat enterprise when it was still using TLSv1.2 instead of TLSv1.3:
https://bugzilla.redhat.com/show_bug.cgi?id=1611815
https://gitlab.com/fetchmail/fetchmail/commit/9b8b634312f169fab872f3580c2febe5af031615
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: sylpheed 3.5.1-1ubuntu3
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Oct 23 00:27:01 2018
InstallationDate: Installed on 2016-06-05 (869 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: sylpheed
UpgradeStatus: Upgraded to cosmic on 2018-10-21 (1 days ago)
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2018-03-20T22:16:27.108498 |
|
| 2019-10-08 20:47:30 |
Dan Streetman |
sylpheed (Ubuntu Eoan): importance |
Undecided |
Medium |
|
| 2019-10-08 20:47:31 |
Dan Streetman |
sylpheed (Ubuntu Disco): importance |
Undecided |
Medium |
|
| 2019-10-08 20:47:34 |
Dan Streetman |
sylpheed (Ubuntu Bionic): importance |
Undecided |
Medium |
|
| 2019-10-08 20:47:39 |
Dan Streetman |
sylpheed (Ubuntu Eoan): status |
Triaged |
In Progress |
|
| 2019-10-08 20:47:41 |
Dan Streetman |
sylpheed (Ubuntu Disco): status |
New |
In Progress |
|
| 2019-10-08 20:47:43 |
Dan Streetman |
sylpheed (Ubuntu Bionic): status |
New |
In Progress |
|
| 2019-10-08 20:47:47 |
Dan Streetman |
sylpheed (Ubuntu Eoan): assignee |
|
Dan Streetman (ddstreet) |
|
| 2019-10-08 20:47:50 |
Dan Streetman |
sylpheed (Ubuntu Bionic): assignee |
|
Dan Streetman (ddstreet) |
|
| 2019-10-08 20:47:53 |
Dan Streetman |
sylpheed (Ubuntu Disco): assignee |
|
Dan Streetman (ddstreet) |
|
| 2019-10-08 21:12:00 |
Robie Basak |
tags |
amd64 apport-bug bionic cosmic patch regression-update |
amd64 apport-bug bionic bionic-openssl-1.1 cosmic patch regression-update |
|
| 2019-10-08 21:56:43 |
Launchpad Janitor |
sylpheed (Ubuntu Eoan): status |
In Progress |
Fix Released |
|
| 2019-10-09 00:29:15 |
Bug Watch Updater |
sylpheed (Debian): status |
Unknown |
Fix Released |
|
| 2019-10-19 16:38:17 |
Moshe Caspi |
bug |
|
|
added subscriber Moshe Caspi |
| 2019-10-24 13:40:57 |
Łukasz Zemczak |
sylpheed (Ubuntu Disco): status |
In Progress |
Fix Committed |
|
| 2019-10-24 13:41:02 |
Łukasz Zemczak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2019-10-24 13:41:05 |
Łukasz Zemczak |
bug |
|
|
added subscriber SRU Verification |
| 2019-10-24 13:41:08 |
Łukasz Zemczak |
tags |
amd64 apport-bug bionic bionic-openssl-1.1 cosmic patch regression-update |
amd64 apport-bug bionic bionic-openssl-1.1 cosmic patch regression-update verification-needed verification-needed-disco |
|
| 2019-10-24 13:41:36 |
Łukasz Zemczak |
removed subscriber Ubuntu Sponsors Team |
|
|
|
| 2019-10-24 13:42:01 |
Łukasz Zemczak |
sylpheed (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
| 2019-10-24 13:42:08 |
Łukasz Zemczak |
tags |
amd64 apport-bug bionic bionic-openssl-1.1 cosmic patch regression-update verification-needed verification-needed-disco |
amd64 apport-bug bionic bionic-openssl-1.1 cosmic patch regression-update verification-needed verification-needed-bionic verification-needed-disco |
|
| 2019-10-25 16:46:29 |
vofka |
summary |
Sypheed not (or no longer) using SNI for SSL connections |
Sylpheed not (or no longer) using SNI for SSL connections |
|
| 2019-10-25 16:48:10 |
vofka |
tags |
amd64 apport-bug bionic bionic-openssl-1.1 cosmic patch regression-update verification-needed verification-needed-bionic verification-needed-disco |
amd64 apport-bug bionic bionic-openssl-1.1 cosmic patch regression-update verification-done-bionic verification-needed verification-needed-disco |
|
| 2019-10-29 08:58:33 |
Dan Streetman |
tags |
amd64 apport-bug bionic bionic-openssl-1.1 cosmic patch regression-update verification-done-bionic verification-needed verification-needed-disco |
amd64 apport-bug bionic bionic-openssl-1.1 patch regression-update verification-done verification-done-bionic verification-done-disco |
|
| 2019-11-04 13:10:33 |
Launchpad Janitor |
sylpheed (Ubuntu Disco): status |
Fix Committed |
Fix Released |
|
| 2019-11-04 13:10:38 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2019-11-04 14:23:01 |
Launchpad Janitor |
sylpheed (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
