<!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 style="color: #777777;">

<a href="https://gitlab.com/Lekensteyn">Peter Wu</a>

commented:

</p>

<div style="">

<p dir="auto">It appears that developers can mess up their implementations and hard-code the priority string <code>NORMAL:-VERS-ALL:+VERS-TLS1.2:+VERS-TLS1.3</code>, resulting in advertising TLS 1.2, TLS 1.3 in the supported_versions extension, see <a href="https://github.com/systemd/systemd/issues/13528" rel="nofollow noreferrer noopener" target="_blank">https://github.com/systemd/systemd/issues/13528</a></p>

<p dir="auto">I cannot think of a secure use case where you want to support both TLS 1.2 and 1.3, but prefer TLS 1.2. And clearly, GnuTLS cannot handle spec-compliant servers that end up agreeing TLS 1.2 and send a downgrade signal (see the previous systemd issue). So what about always advertising TLS 1.3 before 1.2, regardless of the priority string?</p>

</div>

</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/837#note_232986603">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/eda04b68128f60e53576f1d5595490d7/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/837#note_232986603"}}</script>

</p>

</div>

</body>

</html>