<!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="">
<p dir="auto">I wouldn't disable TLS1.3 if these groups are enabled in priority string:</p>
<ul dir="auto">
<li>it would be quite easy to disable TLS1.3 by misconfiguring priority string</li>
<li>it might make a sensible configuration for a server to support TLS1.3 with ECDSA, while falling back to TLS1.2 if client requests GOST cipher suite.</li>
</ul>
<p dir="auto">I'm actually more concerned about the other direction: if client specifies TLS 1.3 and one of these groups (together with other known ones) we should not fail negotiation (currently GnuTLS will return icorrect_parameter, because GOST groups are not supported in key_share extension). So my first target is to ignore these groups when TLS 1.3 is selected.</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/merge_requests/920#note_141500564">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/ccd5de800dd04c4427e08c2adaa9e337/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 Merge request","url":"https://gitlab.com/gnutls/gnutls/merge_requests/920#note_141500564"}}</script>
</p>
</div>
</body>
</html>