<!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=US-ASCII" http-equiv="Content-Type">

<title>

GitLab

</title>

<style>img {

max-width: 100%; height: auto;

}

</style>

</head>

<body>

<div class="content">

<p class="details" style="font-style: italic; color: #777;">

<a href="https://gitlab.com/lumag">Dmitry Eremin-Solenikov</a> created an issue:

</p>

<div></div>

<p dir="auto">For now priority setup will disable TLS 1.3 if 'unsupported' KX is enabled (like SRP or PSK/RSA-PSK). This causes bad effects when adding VKO-GOST KX support, as one can not have <code>-VER-TLS-ALL:+VER-TLS1.3:+KX-ALL</code> setup anymore. It looks like priorities should be handled during SERVER HELLO stage:

if TLS 1.3 is enabled and negotiation fails, switch to older TLS version and try negotiating again.</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/825">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/c51fd59fade1a2a885ad38c23313c36d/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/825"}}</script>

</p>

</div>

</body>

</html>