<!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 class="details" style="font-style: italic; color: #777;">
<a href="https://gitlab.com/lumag">Dmitry Eremin-Solenikov</a> created an issue:
</p>
<div></div>
<p dir="auto">The following discussions from <a href="https://gitlab.com/gnutls/gnutls/merge_requests/1119" data-original="!1119" data-link="false" data-link-reference="false" data-project="179611" data-merge-request="41768515" data-project-path="gnutls/gnutls" data-iid="1119" data-mr-title="Add GOST-CNT ciphersuite support" data-reference-type="merge_request" data-container="body" data-placement="bottom" title="" class="gfm gfm-merge_request">!1119</a> should be addressed:</p>
<ul class="task-list" dir="auto">
<li class="task-list-item">
<p><input type="checkbox" class="task-list-item-checkbox" disabled> <a href="https://gitlab.com/nmav" data-user="105950" data-reference-type="user" data-container="body" data-placement="bottom" class="gfm gfm-project_member" title="Nikos Mavrogiannopoulos">@nmav</a> started a <a href="https://gitlab.com/gnutls/gnutls/merge_requests/1119#note_243928311" data-original="discussion" data-link="true" data-link-reference="true" data-project="179611" data-merge-request="41768515" data-project-path="gnutls/gnutls" data-iid="1119" data-mr-title="Add GOST-CNT ciphersuite support" data-reference-type="merge_request" data-container="body" data-placement="bottom" title="" class="gfm gfm-merge_request">discussion</a>: (+17 comments)</p>
<blockquote>
<p>That's a part which I think is the most questionable in terms of policy. How can we have an implementation which supports GOST but enables it conditionally. For example debian or fedora may want to support GOST but not enable it by default (i.e., enable it via a crypto policy). The reason is that this is a national standard, not widely accepted and enabling by default will trigger pushback to the whole effort of gost support.</p>
</blockquote>
</li>
</ul>
<p dir="auto">For now GOST ciphersuites are going to be merged, but they have to be explicitly enabled on both server (this is more or less fine) and on client (and this ideally should be fixed) sides.</p>
</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/879">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/5ad21de77cbbe0e46e9ce93d0c170bb5/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/879"}}</script>
</p>
</div>
</body>
</html>