[Bug 1799345] Re: Sypheed not (or no longer) using SNI for SSL connections
I've tested 3.5.1-1ubuntu3.18.04.1. This package fixes the bug. ** Summary changed: - Sypheed not (or no longer) using SNI for SSL connections + Sylpheed not (or no longer) using SNI for SSL connections ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799345 Title: Sylpheed not (or no longer) using SNI for SSL connections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sylpheed/+bug/1799345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799345] Re: Sypheed not (or no longer) using SNI for SSL connections
Hello Moses, or anyone else affected, Accepted sylpheed into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/sylpheed/3.5.1-1ubuntu3.19.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: sylpheed (Ubuntu Disco) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-disco ** Changed in: sylpheed (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799345 Title: Sypheed not (or no longer) using SNI for SSL connections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sylpheed/+bug/1799345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799345] Re: Sypheed not (or no longer) using SNI for SSL connections
** Changed in: sylpheed (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799345 Title: Sypheed not (or no longer) using SNI for SSL connections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sylpheed/+bug/1799345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799345] Re: Sypheed not (or no longer) using SNI for SSL connections
This bug was fixed in the package sylpheed - 3.5.1-1ubuntu5 --- sylpheed (3.5.1-1ubuntu5) eoan; urgency=medium * d/p/0009-support-SNI-for-IMAP.patch: add SNI support (LP: #1799345) -- Dan Streetman Tue, 08 Oct 2019 16:36:03 -0400 ** Changed in: sylpheed (Ubuntu Eoan) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799345 Title: Sypheed not (or no longer) using SNI for SSL connections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sylpheed/+bug/1799345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799345] Re: Sypheed not (or no longer) using SNI for SSL connections
** Tags added: bionic-openssl-1.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799345 Title: Sypheed not (or no longer) using SNI for SSL connections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sylpheed/+bug/1799345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799345] Re: Sypheed not (or no longer) using SNI for SSL connections
thanks @vofka! I uploaded to Eoan, Disco, and Bionic so it's waiting for approval now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799345 Title: Sypheed not (or no longer) using SNI for SSL connections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sylpheed/+bug/1799345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799345] Re: Sypheed not (or no longer) using SNI for SSL connections
** Changed in: sylpheed (Ubuntu Eoan) Importance: Undecided => Medium ** Changed in: sylpheed (Ubuntu Disco) Importance: Undecided => Medium ** Changed in: sylpheed (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: sylpheed (Ubuntu Eoan) Status: Triaged => In Progress ** Changed in: sylpheed (Ubuntu Disco) Status: New => In Progress ** Changed in: sylpheed (Ubuntu Bionic) Status: New => In Progress ** Changed in: sylpheed (Ubuntu Eoan) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: sylpheed (Ubuntu Bionic) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: sylpheed (Ubuntu Disco) Assignee: (unassigned) => Dan Streetman (ddstreet) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799345 Title: Sypheed not (or no longer) using SNI for SSL connections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sylpheed/+bug/1799345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799345] Re: Sypheed not (or no longer) using SNI for SSL connections
** Bug watch added: Debian Bug tracker #908063 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908063 ** Also affects: sylpheed via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908063 Importance: Unknown Status: Unknown ** No longer affects: sylpheed ** Also affects: sylpheed (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908063 Importance: Unknown Status: Unknown ** Also affects: sylpheed (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: sylpheed (Ubuntu Eoan) Importance: Undecided Status: Triaged ** Also affects: sylpheed (Ubuntu Disco) Importance: Undecided Status: New ** Description changed: + [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 + [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 ** Tags added: regression-update ** Description changed: [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
[Bug 1799345] Re: Sypheed not (or no longer) using SNI for SSL connections
** Description changed: 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. + 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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799345 Title: Sypheed not (or no longer) using SNI for SSL connections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sylpheed/+bug/1799345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799345] Re: Sypheed not (or no longer) using SNI for SSL connections
Need help with Regression Potential section. I have no idea about possible regressions. According to https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update_the_packaging if you want to fix it in 18.04 you should patch latest version for 18.04 (3.5.1-1ubuntu3) so this is updated debdiff for Bionic applicable to 3.5.1-1ubuntu3. It builds successfully, the patch works as intended. ** Description changed: + 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 ** Tags added: bionic ** Patch 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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799345 Title: Sypheed not (or no longer) using SNI for SSL connections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sylpheed/+bug/1799345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799345] Re: Sypheed not (or no longer) using SNI for SSL connections
Hello. This requires the SRU template and all requisite information including test cases to determine if this is SRUable. Please refer to https://wiki.ubuntu.com/StableReleaseUpdates#Procedure for details. Once you apply the SRU template, if you still need a sponsor for this, please resubscribe ubuntu-sponsors to the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799345 Title: Sypheed not (or no longer) using SNI for SSL connections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sylpheed/+bug/1799345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799345] Re: Sypheed not (or no longer) using SNI for SSL connections
The attachment "1-3.5.1-1ubuntu5.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799345 Title: Sypheed not (or no longer) using SNI for SSL connections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sylpheed/+bug/1799345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799345] Re: Sypheed not (or no longer) using SNI for SSL connections
This was fixed in Debian a year ago with a patch from #2 and is already in stable (buster). This is a debdiff for Bionic applicable to 3.5.1-1ubuntu4. I built this in pbuilder and it builds successfully, and I installed it, the patch works as intended. ** Patch 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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799345 Title: Sypheed not (or no longer) using SNI for SSL connections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sylpheed/+bug/1799345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799345] Re: Sypheed not (or no longer) using SNI for SSL connections
I'm on Lubuntu 18.04.2, and I'm having the same problem with Sylpheed and Gmail. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799345 Title: Sypheed not (or no longer) using SNI for SSL connections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sylpheed/+bug/1799345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799345] Re: Sypheed not (or no longer) using SNI for SSL connections
There is an upstream bug report with a patch, though it's not released yet: https://sylpheed.sraoss.jp/redmine/issues/306 ** Changed in: sylpheed (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799345 Title: Sypheed not (or no longer) using SNI for SSL connections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sylpheed/+bug/1799345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
