[gnutls-devel] GnuTLS | ktls: basic implementation of SW mode (!1451)

[Read-only notification of GnuTLS library development activities]

Richard W_M_ Jones commented:


>From the point of view of a potential user of the API, it would be best to have a way to allow ktls to be used, but not fail if it cannot be used (it is, after all, an optimization).  And if we have that, then why do we need a `set_ktls` option at all?  Just make it happen if it's possible, otherwise fall back to software.

Another way to think about this: If you add the `set_ktls` API, then why **wouldn't** everyone use it all the time?

However it would be nice to have a `get_ktls` function which tells us if kTLS is being used.  We could report that in debugging output in libnbd for example (https://gitlab.com/nbdkit/libnbd/-/blob/72ad5b2ab41e5253901a6e1c8309350a58602462/lib/crypto.c#L699)

-- 
Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/merge_requests/1451#note_680381199
You're receiving this email because of your account on gitlab.com.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.gnupg.org/pipermail/gnutls-devel/attachments/20210917/c261836b/attachment.html>