[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20170615.121311.1238287091540165656.davem@davemloft.net>
Date: Thu, 15 Jun 2017 12:13:11 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: davejwatson@...com
Cc: ilyal@...lanox.com, aviadye@...lanox.com, borisp@...lanox.com,
liranl@...lanox.com, matanb@...lanox.com, netdev@...r.kernel.org,
tom@...bertland.com, herbert@...dor.apana.org.au,
linux-crypto@...r.kernel.org, hannes@...essinduktion.org,
eric.dumazet@...il.com, alexei.starovoitov@...il.com,
nmav@...tls.org, fridolin.pokorny@...il.com
Subject: Re: [PATCH v3 net-next 0/4] kernel TLS
From: Dave Watson <davejwatson@...com>
Date: Wed, 14 Jun 2017 11:36:54 -0700
> This series adds support for kernel TLS encryption over TCP sockets.
> A standard TCP socket is converted to a TLS socket using a setsockopt.
> Only symmetric crypto is done in the kernel, as well as TLS record
> framing. The handshake remains in userspace, and the negotiated
> cipher keys/iv are provided to the TCP socket.
>
> We implemented support for this API in OpenSSL 1.1.0, the code is
> available at https://github.com/Mellanox/tls-openssl/tree/master
>
> It should work with any TLS library with similar modifications,
> a test tool using gnutls is here: https://github.com/Mellanox/tls-af_ktls_tool
>
> RFC patch to openssl:
> https://mta.openssl.org/pipermail/openssl-dev/2017-June/009384.html
...
Series applied, thanks for all of this hard work!
Powered by blists - more mailing lists