<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">

<html lang="en">

<head>

<meta content="text/html; charset=utf-8" http-equiv="Content-Type">

<title>

GitLab

</title>

<style>img {

max-width: 100%; height: auto;

}

</style>

</head>

<body>

<div class="content">

<div>

<p dir="auto">I just had to rewrite my own code for this reason.</p>

<p dir="auto">With TLS 1.3, gnutls will return GNUTLS_E_AGAIN even if the underlying transport socket is a blocking socket. I'm pretty sure that previously GNUTLS_E_AGAIN was getting returned only with non-blocking sockets as the underlying transport, when reading or writing to the socket came back with EAGAIN. GNUTLS_E_AGAIN was, basically, a passthrough for EAGAIN on the underlying socket.</p>

<p dir="auto">All existing code that uses blocking sockets most likely handles any -1 return from gnutls_record_send(), gnutls_record_recv(), and gnutls_handshake() as a fatal transport error. It doesn't know about special meaning of GNUTLS_E_AGAIN, because it was only seen, up until now, with non-blocking sockets.</p>

<p dir="auto">Existing code that uses non-blocking sockets is unlikely to be affected, as it already understands GNUTLS_E_AGAIN.</p>

</div>

</div>

<div class="footer" style="margin-top: 10px;">

<p style="font-size: small; color: #777777;">

—

<br>

Reply to this email directly or <a href="https://gitlab.com/gnutls/gnutls/issues/644#note_123363338">view it on GitLab</a>.

<br>

You're receiving this email because of your account on gitlab.com.

If you'd like to receive fewer emails, you can

<a href="https://gitlab.com/sent_notifications/61afc77b71e46d2310e185f17b8fd1b9/unsubscribe">unsubscribe</a>

from this thread or

adjust your notification settings.

<script type="application/ld+json">{"@context":"http://schema.org","@type":"EmailMessage","action":{"@type":"ViewAction","name":"View Issue","url":"https://gitlab.com/gnutls/gnutls/issues/644#note_123363338"}}</script>

</p>

</div>

</body>

</html>