<!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></div>

<p dir="auto">Currently we handle re-authentication under TLS1.2 (or earlier) on the client side via handling of the <code>GNUTLS_E_REHANDSHAKE</code> error code . Under TLS1.3, the client application must handle the <code>GNUTLS_E_REAUTH_REQUEST</code> by calling <code>gnutls_reauth()</code>. This can result to a lot of code which is tedious for client applications. We should provide a <code>gnutls_init()</code> flag which makes the re-authentication transparent under both TLS1.2 and TLS1.3.</p>

</div>

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

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

—

<br>

Reply to this email directly or <a href="https://gitlab.com/gnutls/gnutls/issues/571">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/e4ede57ba9e25e669c483eb0fc4649ad/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/571"}}</script>

</p>

</div>

</body>

</html>