Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

iks_recv timeout with TLS doesn't work correctly #19

Open
GoogleCodeExporter opened this issue Jul 4, 2015 · 0 comments
Open

iks_recv timeout with TLS doesn't work correctly #19

GoogleCodeExporter opened this issue Jul 4, 2015 · 0 comments

Comments

@GoogleCodeExporter
Copy link

The current trunk code doesn't handle correctly the timeout parameter. When
the timeout expires, "tls_pull" returns 0 (the number of read bytes) but
gnutls interpreters it as the TCP connection was closed. 

To make it behave correctly you have to use errno EAGAIN when returning
from "tls_pull". This change has been made directly to the "io_recv" so
that it behaves correctly in any situation (with or without TLS).

A patch (against r25) is attached to correct this wrong behaviour. It
should be correct.

I see there is a similar problem (with patch) in Issue 10, but the one
attached here is against current trunk.

Original issue reported on code.google.com by emanuele...@mobimesh.it on 4 Nov 2009 at 11:34

Attachments:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant