Any chance of an update of uw-imap for Xenial to fix this issue?
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834340
Title:
Regression for GMail after libssl upgrade with TLSv1.3
To mana
** 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/1834340
Title:
Regression for GMail after libssl upgrade with TLSv1.3
To manage notifications about this bug go to:
h
Thanks for catching that; I just set the packages/releases for those as
Invalid.
** Changed in: asterisk (Ubuntu Bionic)
Status: Incomplete => Invalid
** Changed in: asterisk (Ubuntu Disco)
Status: In Progress => Invalid
** Changed in: mailsync (Ubuntu Bionic)
Status: Incomp
Why does mailsync need a rebuild against the new uw-imap? There is no
test case listed for mailsync here.
** Changed in: mailsync (Ubuntu Bionic)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Why does asterisk need a rebuild against the new uw-imap? There is no
test case listed for asterisk here.
** Changed in: asterisk (Ubuntu Bionic)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
** Changed in: asterisk (Ubuntu Bionic)
Status: New => In Progress
** Changed in: asterisk (Ubuntu Disco)
Status: New => In Progress
** Changed in: asterisk (Ubuntu Disco)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
** Changed in: asterisk (Ubuntu Bionic)
A
** Changed in: uw-imap (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/1834340
Title:
Regression for GMail after libssl upgrade with TLSv1.3
To manage
This bug was fixed in the package asterisk - 1:16.2.1~dfsg-2build2
---
asterisk (1:16.2.1~dfsg-2build2) eoan; urgency=medium
* No change rebuild to pick up libc-client2007e-dev. (LP: #1834340)
-- Mauricio Faria de Oliveira Thu, 29 Aug 2019
09:52:20 -0300
** Changed in: asterisk
This bug was fixed in the package mailsync - 5.2.2-3.1build2
---
mailsync (5.2.2-3.1build2) eoan; urgency=medium
* No change rebuild to pick up libc-client2007e-dev. (LP: #1834340)
-- Mauricio Faria de Oliveira Tue, 13 Aug 2019
11:01:00 -0300
** Changed in: mailsync (Ubuntu Eoa
This bug was fixed in the package prayer - 1.3.5-dfsg1-6build1
---
prayer (1.3.5-dfsg1-6build1) eoan; urgency=medium
* No change rebuild to pick up libc-client2007e-dev. (LP: #1834340)
-- Mauricio Faria de Oliveira Tue, 13 Aug 2019
11:50:43 -0300
** Changed in: prayer (Ubuntu E
sponsored asterisk, prayer, and mailsync for e/d/b
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834340
Title:
Regression for GMail after libssl upgrade with TLSv1.3
To manage notifications about
Attaching updated debdiff for asterisk on Eoan,
which changed versions while we waited uw-imap.
** Patch removed: "asterisk_eoan.debdiff"
https://bugs.launchpad.net/ubuntu/+source/uw-imap/+bug/1834340/+attachment/5282373/+files/asterisk_eoan.debdiff
** Patch added: "asterisk_eoan.debdiff"
This bug was fixed in the package uw-imap - 8:2007f~dfsg-
5ubuntu0.18.04.1
---
uw-imap (8:2007f~dfsg-5ubuntu0.18.04.1) bionic; urgency=medium
* 2014_openssl1.1.1_sni.patch (new): Use SNI when building
with OpenSSL 1.1.1 / TLSv1.3 support, since some servers
(e.g., imap.gmail
This bug was fixed in the package uw-imap - 8:2007f~dfsg-
5ubuntu0.19.04.1
---
uw-imap (8:2007f~dfsg-5ubuntu0.19.04.1) disco; urgency=medium
* 2014_openssl1.1.1_sni.patch (new): Use SNI when building
with OpenSSL 1.1.1 / TLSv1.3 support, since some servers
(e.g., imap.gmail.
Thanks for verifying bionic-proposed @pataquets!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834340
Title:
Regression for GMail after libssl upgrade with TLSv1.3
To manage notifications about th
For documentation purposes.
The patch carried in Ubuntu has been sent to Debian bug 916041 [1].
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916041
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
Verification done for bionic:
---
Performed both command line and PHP code tests above, which worked successfully.
I've done them prior to deployment to production, to fix the issue which
originated this very same bug report.
Packages are now upgraded and after reenabling certificate verification,
Verification done for disco:
---
'mailutil check' successfully connects to gmail,
and prompts for an username, using openssl1.1.1.
$ lsb_release -cs
disco
$ sudo apt-get install libc-client2007e uw-mailutils
...
Get:1 http://archive.ubuntu.com/ubuntu disco-proposed/universe amd64
libc-client200
Verification done for bionic:
---
'mailutil check' successfully connects to gmail,
and prompts for an username, using openssl1.1.1.
$ lsb_release -cs
bionic
$ sudo apt-get install libc-client2007e uw-mailutils
...
Get:1 http://archive.ubuntu.com/ubuntu bionic-proposed/universe amd64
libc-clien
Hello pataquets, or anyone else affected,
Accepted uw-imap into disco-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/uw-imap/8:2007f~dfsg-
5ubuntu0.19.04.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new packa
> So this means the servers that require SNI when using TLSv1.3 can not
(any longer?) be accessed by their direct ip address, their hostname
*must* be used.
SNI, per RFC 6066 is not allowed for IP addresses, so servers couldn't
require it (this is not new in TLSv1.3):
"Literal IPv4 and IPv6 addre
This bug was fixed in the package uw-imap - 8:2007f~dfsg-6ubuntu1
---
uw-imap (8:2007f~dfsg-6ubuntu1) eoan; urgency=medium
* 2014_openssl1.1.1_sni.patch (new): Use SNI when building
with OpenSSL 1.1.1 / TLSv1.3 support, since some servers
(e.g., imap.gmail.com, imap.mail.att
Dan,
Very good point.
Access by IP address didn't work before -- I just checked w/ Xenial / OpenSSL
1.0.0,
and it fails with certification verification error too.
IIUIC this seems reasonable - as the default certificate is the only thing the
server
could send to the client without SNI (which
> Test with an IP address should not send SNI per the patch,
> so it should fail with the certificate verification error:
just to clarify as I was not clear at first:
-with TLSv1.3, some servers (as listed in description, e.g. gmail) require SNI
-if the client is accessing the server via DNS na
For documentation purposes,
Test with an IP address should not send SNI per the patch,
so it should fail with the certificate verification error:
$ mailutil check {imap.gmail.com:993/imap/ssl}INBOX
{cb-in-f108.1e100.net/imap} username:
$ host imap.gmail.com | grep -m1 address
gmail-imap.l.google
** Also affects: uw-imap (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916041
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834340
Ti
** Tags added: sts sts-sponsor sts-sponsor-ddstreet
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834340
Title:
Regression for GMail after libssl upgrade with TLSv1.3
To manage notifications about
** Also affects: asterisk (Ubuntu)
Importance: Undecided
Status: New
** Also affects: mailsync (Ubuntu)
Importance: Undecided
Status: New
** Also affects: prayer (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a memb
28 matches
Mail list logo