Bug 533647 - tls_socket_read
Summary: tls_socket_read
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: mutt
Version: 12
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Miroslav Lichvar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-11-08 04:53 UTC by eric
Modified: 2013-02-01 04:54 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-12-04 03:27:27 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description eric 2009-11-08 04:53:31 UTC
Description of problem: When logging into Mutt I will sometimes receive an error message at the bottom of the screen:

tls_socket_read(A TLS packet with unexpected length was received.) 

I will sometimes receive this error after logging in and working with email.

After receiving this message Mutt generally crashes and I have to restart the program.


Version-Release number of selected component (if applicable): 5:1.5.20-1.20090827hg605559.fc12


How reproducible: Almost always


Steps to Reproduce:
1. Log into Mutt
2. Wait
  
Actual results:
Receive tls socket read error


Expected results:
Mutt works.

Additional info:
The account Mutt is logging into is an IMAP account.

Comment 1 Miroslav Lichvar 2009-11-09 08:34:17 UTC
This looks like a gnutls problem

https://savannah.gnu.org/support/index.php?106987

Comment 2 Tomas Mraz 2009-11-09 10:09:31 UTC
I am not quite sure  that it is a gnutls problem. It might be a problem with how mutt calls gnutls or how it reacts to the protocol error gnutls reports.

Comment 3 Tomas Mraz 2009-11-09 20:18:30 UTC
I've tried the steps from the savannah bug report and it really looks like the gmail pop3s doesn't terminate the connection properly that is it aborts the connection without sending the appropriate TLS shutdown packet.

I do not think that mutt should crash after this error. It should probably just attempt to reconnect.

Comment 4 eric 2009-11-09 21:55:48 UTC
It does TRY to reconnect but just bombs out and cycles.  It's more like a perpetual cycling.

Comment 5 eric 2009-11-09 22:17:28 UTC
Okay, so when I get the error, mutt closes the mailbox and then attempts to log back in but just hangs there.  Right now it just say "Logging in..." so not really a crash so much as a hang.

Comment 6 Joe Orton 2009-11-10 08:59:12 UTC
You get an GNUTLS_E_UNEXPECTED_PACKET_LENGTH error from gnutls for a premature EOF (i.e. without a clean TLS shutdown).

Comment 7 Miroslav Lichvar 2009-12-16 13:43:53 UTC
I tried using gmail pops and imaps for a while, but I can't reproduce it.

Does it happen after a longer period of idling or while reading mails? 

Can you try to make a backtrace when mutt is hung?

Comment 8 Bug Zapper 2010-11-04 06:42:30 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 9 Bug Zapper 2010-12-04 03:27:27 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.