<!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>

<p dir="auto"><a href="https://gitlab.com/caldwell" data-user="675594" data-reference-type="user" data-container="body" data-placement="bottom" class="gfm gfm-project_member has-tooltip" title="David Caldwell">@caldwell</a> Maybe this should be moved to a broader audience, e.g. as an MR to <a href="https://github.com/tomato42/tlsfuzzer" rel="nofollow noreferrer noopener" target="_blank">https://github.com/tomato42/tlsfuzzer</a>. I guess more or less every TLS implementation uses that test suite (or will do in the future).</p>

<p dir="auto">It would be indeed good if TLS vendors agree on handling this issue(s), be it creating or consuming certificates. GnuTLS would then follow the general agreement (I guess).</p>

<p dir="auto">It would be good if you bring up such an MR, so there are immediate example(s) to test with.

Just link in this discussion or copy&paste, whatever is more appropriate to you.</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/553#note_101905198">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/31a05ee78cccd0c9f0b78dd9f86b1aef/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/553#note_101905198"}}</script>

</p>

</div>

</body>

</html>