It is indeed a GnuTLS bug. It can be reproduced using only gnutls-cli:
gnutls-cli pop.verizon.net -p 995
gnutls-cli imap.aol.com -p 993
I can reproduce it with gnutls28 (jessie), but not gnutls26 (wheezy). Those
covered the jump from 2.2.6 to 3.0.0, where they changed from libgcrypt to
nettle, so not that strange they have different behavior.
The problem was not added by a recent Ubuntu update. It's a bug which was
present in the past, and that only now is being exposed by whatever Yahoo
changed.
Gmail servers doesn't expose it.
Thunderbird is not affected since it uses NSS, not GnuTLS.
As a workaround, affected users could run on a separate terminal a command such
as
socat tcp-listen:9950,fork
openssl-connect:pop.verizon.net:995,capath=/etc/ssl/certs
and then configure evolution to connect to localhost:9950 (without TLS) instead
of pop.verizon.net:995. This way, the actual encryption is performed by
socat... using openssl.
** Also affects: gnutls28 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876286
Title:
Evolution reports "Error performing TLS handshake: Internal error in
memory allocation."
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/claws-mail/+bug/1876286/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
