Created attachment 763650 [details] SslStream patch Description of problem: System.Net.Security.SslStream hangs in AuthenticateAsServer. Version-Release number of selected component (if applicable): mono-2.10, mono-2.4 (from EPEL) also affected. How reproducible: Always. Steps to Reproduce: 1. Server application uses SslStream.AuthenticateAsServer: SslStream stream = new SslStream(new NetworkStream(socket)); Console.Error.WriteLine("Starting handshake as server"); stream.AuthenticateAsServer(x509cert2); // <-- Hangs here until client sends data Console.Error.WriteLine("Complete handshake as server"); 2. Client app uses AuthenticateAsClient SslStream stream = new SslStream(new NetworkStream(socket)); Console.Error.WriteLine("Starting handshake as client"); stream.AuthenticateAsClient("servername"); Console.Error.WriteLine("Complete handshake as client"); Actual results: On the client side, SslStream.AuthenticateAsClient completes OK. On the server side, SslStream.AuthenticateAsServer hangs until client sends data. After client send any data, servers' SslStream.AuthenticateAsServer completes with success. The problem is when client app waits from a server some data in order to start session (i.e. like SMTP - client connects to server, waits for "220 OK" and then sends HELO/EHLO). Expected results: On the server side, SslStream.AuthenticateAsServer must return success after handshake complete successful. Additional info: The problem is hard to detect, because it's rare case when client after SSL handshake waits reply from a server, but when this style is required, problem became critical. The problem is very old - http://www.mail-archive.com/mono-bugs@lists.ximian.com/msg87637.html There is a short fix for this bug, a tiny patch included.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 '18'. 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 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. 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.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.