Public bug reported:
When Evolution checks my verizon.net account it displays the message
"Error performing TLS handshake: Internal error in memory allocation"
and doesn't download any new email messages. This started happening two
days ago shortly after updates were applied. Normally it would
I haven't been able to get the pop3 debug logging to work. Maybe one of
the developers could try to add another account with a pop connection to
verizon from a fully patched 18.04 machine? The verizon.net settings
are:
Server: pop.verizon.net
Port: 995
Encryption
Joe,
If your not sure if there is any sensitive information in the trace
please do not send the files. I was able to get wireshark to decrypt
and decode the pcap and was certain that no username/password was
recorded in the files I posted.
The next logical step would be to get the source code,
Joe,
Thanks for the info! I made some progress on this today. Evidently Evolution
uses GnuTLS to communicate with the pop server. If you run the following
commands on a terminal you should get plenty of output that will allow you to
decode the encrypted packets:
export
The issue appears to be in /usr/lib/x86_64-linux-
gnu/libgnutls.so.30.14.10 with the function
_gnutls_recv_new_session_ticket around line 758 of session_ticket.c.
The code reads two bytes and assigns the result to the variable
ticket_len. Unfortunately this value is zero. A few lines later when
I looked into upgrading from Ubuntu 18.04 to 20.04 but evidently that isn't an
option until sometime in July. I tried to install the flatpack version and was
able to get to all my email accounts again. Before trying this make sure to
backup your current evolution data (File, Backup Evolution
I used the built in backup on the file menu, "Backup Evolution Data
...". The following output appeared:
evolution-backup-Message: 18:00:36.504: dconf dump
/org/gnome/evolution-data-server/
>/home/user/.local/share/evolution/backup-restore-dconf-eds.ini
evolution-backup-Message: 18:00:36.537:
Daiki Ueno from the GnuTLS accepted my merge request (1260) that fixes this
problem. Can Ubuntu backport the changes to 18.04 and 16.04?
https://gitlab.com/gnutls/gnutls/-/merge_requests/1260
** Changed in: gnutls28 (Ubuntu)
Status: New => Confirmed
--
You received this bug
** Bug watch added: Red Hat Bugzilla #1838187
https://bugzilla.redhat.com/show_bug.cgi?id=1838187
** Also affects: gnutls28 (CentOS) via
https://bugzilla.redhat.com/show_bug.cgi?id=1838187
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are
Joe - I'm glad to hear that it is working and that Debian has also
updated their code. I'm glad that it helped others!
--
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
@magnum6 glad to hear yahoo is working. Did you try using gnutls-cli to
connect to bestweb.net? You didn't specify the full name and port so I
can't try it here. If you try on your end and see a message about
simple client mode towards the end of the output then you have passed
the handshake
Joe, It's still in the proposed repo and hasn't made it to updates yet. Did
you try the instuctions here:
https://wiki.ubuntu.com/Testing/EnableProposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Joe, I’m glad to hear that it works! FYI, Ubuntu rolls out updates slowly
starting with 10% of users, increasing 10% every 6 hours if there are no
problems. This may explain why it took some time before you saw the update.
Everyone should have been able to apply the updates on Sunday.
@seb128 just checking to make sure that your not waiting for something
on my end. If I understand it correctly it looks like Focal is done
since you re-ran the systemd test and now all tests have passed, and I
verified that the fix worked. Should the tag be updated to
verification-done-focal?
Awesome, thanks Sebastien! FYI - the original patch I submitted to the
GnuTLS project was for Ubuntu 18.04.4 with the gnutls28-3.5.18 package.
Daiki asked for some minor changes to that patch and to apply it to the
current development tree. I'm at work right now but when I'm done I
will work on
Patch for Ubuntu 18.04/3.5.18 attached.
Note: testing with gnutls-cli worked with the following command:
gnutls-cli pop.verizon.net:995
** Patch added: "Patch for Ubuntu 18.04/3.5.18 attached."
Patch for Ubuntu 18.04/3.5.18 attached.
Note: testing with gnutls-cli worked with the following command:
gnutls-cli pop.verizon.net:995
** Patch added: "Patch for Ubuntu 18.04/3.5.18 attached."
@seb128 - Excellent, thank you! Other users have reported the same
issue against different versions of Ubuntu. I believe that Eoan and
Xenial are the other two supported versions. I would be willing to
looking into those versions and see what changes are necessary. Would
those be separate
Patch for Ubuntu 16.04/3.4.10 attached.
Note: testing with gnutls-cli worked with the following command:
gnutls-cli -p 995 pop.verizon.net
** Patch added: "Patch for Ubuntu 16.04/3.4.10"
@stephenholden could you provide:
1) details on your connection type (pop/imap), server and port (in my
case this was pop to pop.verizon.net on port 995).
2) output of "dpkg -l | grep gnutls"
3) test my server using "gnutls-cli pop.verizon.net:995" (you may need
to install the gnutls-bin
@@stephenholden both of these have to be updated. This is where the
code change was made:
ii libgnutls30:amd64 3.5.18-1ubuntu1.3
amd64GNU TLS library - main
runtime library
ii libgnutls30:i386
@sil2100 - I'm able to confirm the bionic-proposed updates worked for
pop connections to pop.verizon.net on port 995. I started with a fresh
install of Ubuntu 18.04 and applied all updates except proposed. As
expected gnutls-cli and evolution returned the error. After installing
the proposed
@smnbldwn it looks like the Xenial fix was also built for powerpc and
ppc64el
--
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:
@seb128 - Awesome! I will check back after work.
--
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
@seb128 can you double check my thinking? It looks like the regressions on
Bionic with glib-networking/2.56.0-1 are related to newer versions of GnuTLS
reporting GNUTLS_CERT_INSECURE_ALGORITHM on the test certificates. Michael
Catanzaro posted a patch on 2018-04-11 on comment 3 at:
I'm able to confirm the focal-proposed updates/3.6.13-2ubuntu1.2 worked for pop
connections to pop.verizon.net on port 995. I started with a fresh install of
Ubuntu 20.04 and applied all updates except proposed. In order to make GnuTLS
3.6 use an older version of TLS I created the file
Cool! I updated the description. Let me know what you think.
--
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
** Description changed:
[Impact]
Evolution and Claws email clients stopped connecting to Yahoo, AOL,
Verizon, AT, Bell South, etc email servers which are run by the same
- group. Users are unable to get to their email.
+ group. Users are unable to get to their email.
+
+ The underlying
I'm able to confirm the xenial-proposed updates/3.4.10-4ubuntu1.8 worked
for pop connections to pop.verizon.net on port 995. I started with a
fresh install of Ubuntu 16.04 and applied all updates except proposed.
As expected gnutls-cli and evolution returned the error. After
installing the
Big shout out to Daiki Ueno and Andreas Metzler of the GnuTLS project
and everyone on this thread for helping out! Testing with Debian
Bullseye and Ubuntu Groovy + proposed repo was successful. Both
included version 3.6.13-4 of GnuTLS. Hopefully it won't be much longer
before this fix is pushed
Sebastien,
I believe that something on the Yahoo/AOL/etc server side was changed to return
a zero length session ticket for older TLS protocols. According to
https://gnutls.org/manual/html_node/Session-tickets.html:
"A disadvantage of session tickets is that they eliminate the effects of
31 matches
Mail list logo
