<!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 style="">

<blockquote dir="auto">

<p>Maybe the patch could be a clarification that false start and early start (applies to tls1.3 servers), cannot be used by concurrent sending and receiving applications without some synchronization.</p>

</blockquote>

<p dir="auto">That would be a welcome addition indeed</p>

<blockquote dir="auto">

<p>An alternative fix could be to add locking in gnutls recv and send operations internally for this specific case.</p>

</blockquote>

<p dir="auto">That might be a good idea. IIUC once the handshake is completed, any thread can send/write, so it might not be a too broad of a change.</p>

<p dir="auto">I guess the path to be chosen is up to you :)</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/713#note_144106888">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/f8330400f15aa5d1ec5c5aed2f23ef5f/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/713#note_144106888"}}</script>

</p>

</div>

</body>

</html>