[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170616135846.6d6011db@xeon-e3>
Date: Fri, 16 Jun 2017 13:58:46 -0700
From: Stephen Hemminger <stephen@...workplumber.org>
To: Dave Watson <davejwatson@...com>
Cc: Ilya Lesokhin <ilyal@...lanox.com>,
Aviad Yehezkel <aviadye@...lanox.com>,
Boris Pismenny <borisp@...lanox.com>,
Liran Liss <liranl@...lanox.com>,
Matan Barak <matanb@...lanox.com>,
David Miller <davem@...emloft.net>, <netdev@...r.kernel.org>,
Tom Herbert <tom@...bertland.com>,
<herbert@...dor.apana.org.au>, <linux-crypto@...r.kernel.org>,
Hannes Frederic Sowa <hannes@...essinduktion.org>,
Eric Dumazet <eric.dumazet@...il.com>,
Alexei Starovoitov <alexei.starovoitov@...il.com>,
<nmav@...tls.org>, <fridolin.pokorny@...il.com>
Subject: Re: [PATCH v3 net-next 3/4] tls: kernel TLS support
On Wed, 14 Jun 2017 11:37:39 -0700
Dave Watson <davejwatson@...com> wrote:
> --- /dev/null
> +++ b/net/tls/Kconfig
> @@ -0,0 +1,12 @@
> +#
> +# TLS configuration
> +#
> +config TLS
> + tristate "Transport Layer Security support"
> + depends on NET
> + default m
> + ---help---
> + Enable kernel support for TLS protocol. This allows symmetric
> + encryption handling of the TLS protocol to be done in-kernel.
> +
> + If unsure, say M.
I understand that this will be useful to lots of people and most distributions
will enable it. But the defacto policy in kernel configuration has been that
new features in kernel default to being disabled.
Powered by blists - more mailing lists