<!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">Under TLS <1.3 we use the <code>mod_auth_st</code> to define authentication mechanisms and have a nice abstraction mechanism to delegate authentication handling routines to different functions. In TLS 1.3 code this mechanism has been removed. I think this is a regression in code versatility. Since we are adding new authentication mechanisms (Raw public-keys recently and Kerberos in the near future) we are going to need this <code>mod_auth_st</code> again. The RawPK code happened to work under the new system but this is actually a coincidence and the current code path for TLS 1.3 is a bit less efficient than the path for TLS <1.3.</p>
<p dir="auto">I'm curious why <code>mod_auth_st</code> is not used in TLS 1.3 code? If there are no objections I would like to reintroduce it in order to be able to implement TLS-KDH and optimize Raw public-key code.</p>
</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/issues/650">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/63c43e095bceb9c777d60676fb77244e/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/650"}}</script>
</p>
</div>
</body>
</html>