Thanks Graham for the quick turnaround here!
Looks like builds are all green now; any chance to get this merged? :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055398
Title:
Please drop
Debian have updated to 3.1.10 in experimental, but if that's not an
option for noble, the following one-line cmakefile change could also be
backported:
https://github.com/AcademySoftwareFoundation/Imath/pull/361/files
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
Debian have reverted the dependency of libimath-dev on python3-imap and
applied a fix from upstream: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=1061327
Aside from the reasons outlined there, this also cuts down on a lot of
dependency clutter, because installing e.g.
> 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
Another small update to the patch, just in case anyone wants to build it
against OpenSSL versions older than 1.0.2 (let's say on Ubuntu 12.04).
It now checks for the OpenSSL version instead of for
SSL_CTRL_SET_TLSEXT_HOSTNAME (which has been around since
0.9.8.something, so this change is safe in
** Patch removed: "uw-imap-sni.patch"
https://bugs.launchpad.net/ubuntu/+source/uw-imap/+bug/1834340/+attachment/5280829/+files/uw-imap-sni.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
New patch that's RFC 6066 compliant (SNI may only be done for hostnames,
not for IP addresses).
** Patch added: "new patch, RFC6066 compliant"
https://bugs.launchpad.net/ubuntu/+source/uw-imap/+bug/1834340/+attachment/5280961/+files/uw-imap-sni.patch
--
You received this bug notification
Here's a patch.
Before, when connecting to GMail IMAP with PHP:
root@39f3acd3838c:/app# php -r
'imap_open("{imap.gmail.com:993/imap/ssl}INBOX", "user", "pass") or
die(imap_last_error());'
Warning: imap_open(): Couldn't open stream
{imap.googlemail.com:993/imap/ssl}INBOX in /app/imap.php on
For some clarification: this is due to the upgrade to openssl 1.1.1 in
bionic-upgrades, which includes TLSv1.3 support. This leads to
connections being negotiated als TLSv1.3, and Google's IMAP servers
reject the connection (by returning an invalid certificate with a
message) if the attempt is not
