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

<div style="">

<p dir="auto">Thanks, but looking at it again, it seems that ciphers can also be registered externally by the application using <code>gnutls_crypto_register_cipher</code> and even internally we register ciphers using <code>gnutls_crypto_single_cipher_register</code> in <code>lib/accelerated</code>. In these ciphers the <code>get_iv</code> pointer will not be set. I'm not sure what's the best approach here. Maybe we should prohibit this API for anything else than CFB (which is only internally defined), and also prohibit registering CFB when the <code>get_iv</code> is not set. What do you think?</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/merge_requests/988#note_165928917">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/12dc11565b85f32fc47a266d14c0eb2d/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 Merge request","url":"https://gitlab.com/gnutls/gnutls/merge_requests/988#note_165928917"}}</script>

</p>

</div>

</body>

</html>