<!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/richardfm">Richard Frith-Macdonald</a>

commented:

</p>

<div style="">

<p dir="auto">I would class it as a configuration error,  but one that people in my company referred to me as a GNUTLS bug, because they had successfully used our client software to connect to external openssl based servers, but had found that the same client software (configured the same way) had failed to establish a connection to our internal (gnutls based) servers.

So the real issue is not that there is a use case (we don't specifically want to configure 1.2 before 1.3 in the client), but that if it's done accidentally the connection attempt fails and it's not obvious why.</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_220728160">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/85697d23e7faf57b05871c14044a1dbd/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_220728160"}}</script>

</p>

</div>

</body>

</html>