[Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
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 reports "Error performing TLS handshake: Internal error in memory allocation." To manage notifications about this bug go to: https://bugs.launchpad.net/gnutls/+bug/1876286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
@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. Details are here: https://wiki.ubuntu.com/StableReleaseUpdates#Phasing As for other distro’s I think it is time someone else takes over. At this point is should be more of an administrative process since the problem has been pinpointed and patches were made for one distro. You will probably have to file a bug report, point back to this bug and follow their procedures. Worst case the patches may have to be updated slightly to account for different line numbers. -- 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/gnutls/+bug/1876286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
@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? I’m guessing that the Xenial and Bionic fixes are waiting on the glib-networking testing certificate updates we talked about a few days ago. It looks like Alex Murray accepted the changes on Monday and they are making their way through the system. -- 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/gnutls/+bug/1876286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
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. 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/gnutls/+bug/1876286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
@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 part of the connection and there is a different problem with that ISP. -- 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/gnutls/+bug/1876286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
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 /etc/gnutls/config with the following contents: [overrides] default-priority-string = NORMAL:-VERS-TLS1.3 As expected gnutls-cli and evolution returned the error. After installing the proposed versions of libgnutls30 and gnutls-bin I was able to connect to the server with both programs. I also used gnutls-cli to connect to imap.aol.com port 993 as a second check to make sure the new code supports zero length tickets. I also tried port 443 on www.yahoo.com, www.google.com, www.microsoft.com, and www.cnn.com as regression tests. All tests connected to the server and started simple client mode. No errors were displayed. Wireshark confirmed that the connections were using TLS 1.2 and that the aol and verizon servers returned zero length tickets. -- 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/gnutls/+bug/1876286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
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 proposed versions of libgnutls30 and gnutls-bin I was able to connect to the server with both programs. I also used gnutls-cli to connect to imap.aol.com port 993 as a second check to make sure the new code supports zero length tickets. I also tried port 443 on www.yahoo.com, www.google.com, www.microsoft.com, and www.cnn.com as regression tests. All tests connected to the server and started simple client mode. No errors were displayed. -- 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/gnutls/+bug/1876286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
@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 allocation." To manage notifications about this bug go to: https://bugs.launchpad.net/gnutls/+bug/1876286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
@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: https://bugzilla.gnome.org/show_bug.cgi?id=794286#c3 This fixed test 3/8 certificate after applying the patch, generating the certs (tls/tests/files/create-files.sh) and building the package. Test 4/8 file-database failed with the same error. It looks like tls/tests/files/ca-verisign-sha1.pem was signed with sha1 and also needs to be updated. I believe this indicates the tests are no longer valid and is unrelated to the changes I made. How do you want to handle this? ** Bug watch added: bugzilla.gnome.org/ #794286 https://bugzilla.gnome.org/show_bug.cgi?id=794286 -- 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/gnutls/+bug/1876286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
@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: Internal error in memory allocation." To manage notifications about this bug go to: https://bugs.launchpad.net/gnutls/+bug/1876286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
@@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 3.5.18-1ubuntu1.3 i386 GNU TLS library - main runtime library -- 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/gnutls/+bug/1876286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
@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 versions of libgnutls30 and gnutls-bin I was able to connect to the server with both programs. I also used gnutls-cli to connect to imap.aol.com:993 as a second check to make sure the new code supports zero length tickets. I also tried www.yahoo.com:443 www.google.com:443 www.microsoft.com:443 and www.cnn.com:443 as regression tests. All tests connected to the server and started simple client mode. No errors were displayed. -- 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/gnutls/+bug/1876286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
@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 package) and let me know if you see the error or a message that ends with "+OK Hello from jpop-0.1" I just tried with the proposed repo and was able to connect, details in another comment. -- 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/gnutls/+bug/1876286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
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 memory allocation." To manage notifications about this bug go to: https://bugs.launchpad.net/gnutls/+bug/1876286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
** 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 problem is that GnuTLS does not support zero length + session tickets. The fix works by checking that that ticket_len > 0 + prior to calling gnutls_realloc_fast(). Nominating for SRU, fulfills: "Updates that need to be applied to Ubuntu packages to adjust to changes in the environment, server protocols, web services, and similar, i. e. where the current version just ceases to work." + [testcase] + GnuTLS 3.6: $ gnutls-cli --priority=NORMAL:-VERS-TLS1.3 pop.verizon.net:995 [...] - Status: The certificate is trusted. *** Fatal error: Internal error in memory allocation. the error should be fixed with the update + GnuTLS 3.5: + $ gnutls-cli pop.verizon.net:995 + + GnuTLS 3.4: + $ gnutls-cli -p 995 pop.verizon.net + + [regression potential] - check that connecting to website in e.g epiphany and to email accounts in evolution still work correctly + + The fix works by checking that that ticket_len > 0 prior to calling + gnutls_realloc_fast(). This creates two separate execution paths: + + 1) If the session ticket length > 0, which is the primary use case, the + original code block will be executed. + + 2) If the session ticket len is 0, then the original code block will be + skipped. + + Testing will need to include connections to servers that return session + ticket length > 0 as well as ones that return session ticket length of + 0. Wireshark can be used to look at the NewSessionTicket handshake + message to confirm the session ticket length. + + + [Other Info] + + The GnuTLS project's merge request 1260 fixes this bug. It was reviewed and approved by Daiki Ueno: + https://gitlab.com/gnutls/gnutls/-/merge_requests/1260 + + According to the GnuTLS project: "We utilize two continuous integration systems, the gitlab-ci and travis. Gitlab-CI is used to test most of the Linux systems (see .gitlab-ci.yml), and is split in two phases, build image creation and compilation/test. The build image creation is done at the gnutls/build-images subproject and uploads the image at the gitlab.com container registry. The compilation/test phase is on every commit to gnutls project." + Here are the results of the gitlab-ci pipeline showing all 19 tests passed for merge request 1260: + https://gitlab.com/rrivers2/gnutls/-/pipelines/149155018 + + Page 8, section 3.3 of RFC5077 describes the NewSessionTicket handshake message and indicates that a zero length session ticket is a legitimate value: + https://tools.ietf.org/pdf/rfc5077.pdf -- + When GnuTLS connects to servers that return zero length session tickets + using older TLS versions it returns the error code GNUTLS_E_MEMORY_ERROR + and the connection is closed. This prevents Evolution and Claws email + clients from connecting to Yahoo, AOL, Verizon, AT, Bell South, etc + email servers. Evolution displays the message "Error performing TLS + handshake: Internal error in memory allocation" - 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 download the new email messages. Searching the web I found a Linux Mint forum with users having the same issue. Some users felt it maybe an expired certificate while others thought it might be related to the recent update. What can I do to get more information about this issue? ProblemType: Bug DistroRelease: Ubuntu 18.04 - Package: evolution 3.28.5-0ubuntu0.18.04.2 + Package: libgnutls30 3.5.18-1ubuntu1.3 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME - Date: Fri May 1 07:03:51 2020 + Date: Fri May 1 07:03:51 2020 InstallationDate: Installed on 2017-12-12 (870 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: - PATH=(custom, no username) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash - SourcePackage: evolution + PATH=(custom, no username) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + SourcePackage: gnutls28 UpgradeStatus: Upgraded to bionic on 2018-12-28 (489 days ago) -- 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:
[Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
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" https://bugs.launchpad.net/ubuntu/focal/+source/gnutls28/+bug/1876286/+attachment/5384839/+files/51_allow_zero_length_session_tickets.patch -- 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/gnutls/+bug/1876286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
@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 SRU’s or can all three be done in a single SRU? Also, I'm still working on the updates to the description and regression sections you requested. -- 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/gnutls/+bug/1876286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
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." https://bugs.launchpad.net/ubuntu/focal/+source/gnutls28/+bug/1876286/+attachment/5384231/+files/50_allow_zero_length_session_tickets.patch -- 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/gnutls/+bug/1876286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
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." https://bugs.launchpad.net/ubuntu/focal/+source/gnutls28/+bug/1876286/+attachment/5384230/+files/50_allow_zero_length_session_tickets.patch -- 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/gnutls/+bug/1876286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
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 a new patch, make the changes Daiki requested and test with a fully patched Ubuntu 18.04 VM. If everything goes well you should see something tomorrow. As for the source code, I was planning on using "apt source gnutls28" on the VM to make sure I have the exact version Ubuntu has in the current repo. Thanks again, Rod -- 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/gnutls/+bug/1876286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
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 forward secrecy when a server uses the same key for long time. That is, the secrecy of all sessions on a server using tickets depends on the ticket key being kept secret. For that reason server keys should be rotated and discarded regularly. [snip] Under TLS 1.3 session tickets are mandatory for session resumption, and they do not share the forward secrecy concerns as with TLS 1.2 or earlier." My guess is that they felt this was insecure and return a zero length session ticket as a workaround. If more servers are configured that way this will become a bigger problem including more programs than just Evolution and Claws email clients. RFC5077 states "If the server determines that it does not want to include a ticket after it has included the SessionTicket extension in the ServerHello, then it sends a zero-length ticket in the NewSessionTicket handshake message." A zero length ticket is a legitimate value and should be supported. Testing with the current version of OpenSSL on Ubuntu 18.04.4 (1.1.1-1ubuntu2.1~18.04.5) showed that it is able to handle zero length session tickets and wireshark confirmed that the server returned a zero length ticket with the following command: $ openssl s_client -msg -tls1_2 -connect pop.verizon.net:995 This is the first time I have gone through this process. Please let me know if I missed something or did something wrong. I'm trying to follow the SRU wiki entry: https://wiki.ubuntu.com/StableReleaseUpdates If I'm reading this correctly this bug falls under the last bullet of section "2.1 High-impact bugs" which states "Updates that need to be applied to Ubuntu packages to adjust to changes in the environment, server protocols, web services, and similar, i. e. where the current version just ceases to work." I believe the following two conditions have been met: 3.1 Check that the bug is fixed in the current development release, and that its bug task is "Fix Released" 3.2 Ensure that the bug report for this issue is public I'm working on 3.3 and modified the description with the first cut at an impact statement. I'm not sure what to put for the [Regression Potential] section. Any help that you can provide will be greatly appreciated! Thanks, Rod ** 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. + + Nominating for SRU, fulfills: "Updates that need to be applied to Ubuntu + packages to adjust to changes in the environment, server protocols, web + services, and similar, i. e. where the current version just ceases to + work." + [testcase] $ gnutls-cli --priority=NORMAL:-VERS-TLS1.3 pop.verizon.net:995 [...] - Status: The certificate is trusted. *** Fatal error: Internal error in memory allocation. - 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 download the new email messages. Searching the web I found a Linux Mint forum with users having the same issue. Some users felt it maybe an expired certificate while others thought it might be related to the recent update. What can I do to get more information about this issue? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evolution 3.28.5-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri May 1 07:03:51 2020 InstallationDate: Installed on 2017-12-12 (870 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: Upgraded to bionic on 2018-12-28 (489 days ago) -- 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/gnutls/+bug/1876286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
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 out to a wider audience. -- 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/gnutls/+bug/1876286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
** 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 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/gnutls/+bug/1876286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
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 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/gnutls/+bug/1876286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
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 the variable is used in a memory allocation call, the call fails and the code returns GNUTLS_E_MEMORY_ERROR. I'm not sure what is causing the value to be zero. Attached is a copy of the gdb output, maybe someone who is familiar with GnuTLS can help. ** Attachment added: "gdb.txt" https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1876286/+attachment/5369555/+files/gdb.txt -- 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/evolution/+bug/1876286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
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: dconf dump /org/gnome/evolution/ >/home/user/.local/share/evolution/backup- restore-dconf-evo.ini evolution-backup-Message: 18:00:36.605: cd /home/user && tar chf - .local/share/evolution .config/evolution evolution.dir | gzip > '/home/user/evolution-backup-20200508.tar.gz' evolution-backup-Message: 18:12:05.909: rm /home/user/evolution.dir On Fri, 2020-05-08 at 23:10 +, Yi Li wrote: > @Rob > > Did you know where the evolution data is located? > -- 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/evolution/+bug/1876286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
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 data ...). Then I followed the directions at the link below, make sure to follow the setup guide at the top: https://flathub.org/apps/details/org.gnome.Evolution -- 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/evolution/+bug/1876286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
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, compile it and see if you can trace through it to find the line that is failing. I looked at the build instructions but they look complicated: https://wiki.gnome.org/Apps/Evolution/Building At this point I'm looking into either upgrading to Ubuntu 20.04 or installing the flatpack version that was mentioned in the Linux Mint forum. Rod -- 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/evolution/+bug/1876286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
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 GNUTLS_DEBUG_LEVEL=99 evolution It looks like the handshake has just finished and the pop server is returning its first message: Post Office Protocol +OK Hello from jpop-0.1\r\n Response indicator: +OK Response description: Hello from jpop-0.1 I have attached the pcap, debug output and keys. Rod ** Attachment added: "EvolutionVerizonHandshakeFailure.zip" https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1876286/+attachment/5367101/+files/EvolutionVerizonHandshakeFailure.zip -- 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/evolution/+bug/1876286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
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 method: TLS on a dedicated port Authentication: password The Evolution wiki has instructions on debugging the mail backends. I tried to follow the instructions for pop3 but the logfile created had a length of 0. I tried to cut and paste from the wiki into a terminal to make sure there aren't any typos but had the same result. I noticed later on that page there is an all option. That worked but the entries were mostly imapx or DB. I couldn't find any pop logs or anything with TLS. Here is the link to the directions: https://wiki.gnome.org/Apps/Evolution/Debugging Wireshark shows a TLS connection made to pop.verizon.net (66.218.85.35). I can see the server cert chain. Towards the end of the connection there is a small amount of data returned by the server to which the client responds with a reset. Let me know if there are any other logs I can collect, anything else to try on my end or if there is any other information you need to duplicate the issue. -- 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/evolution/+bug/1876286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876286] [NEW] Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
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 download the new email messages. Searching the web I found a Linux Mint forum with users having the same issue. Some users felt it maybe an expired certificate while others thought it might be related to the recent update. What can I do to get more information about this issue? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evolution 3.28.5-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri May 1 07:03:51 2020 InstallationDate: Installed on 2017-12-12 (870 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: Upgraded to bionic on 2018-12-28 (489 days ago) ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- 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/evolution/+bug/1876286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
