[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANn89iK-dzwehweSZxVJ1z9YEYnhFMM3URYpARbxr4bUa1Nskg@mail.gmail.com>
Date: Wed, 18 Oct 2017 13:37:27 -0700
From: Eric Dumazet <edumazet@...gle.com>
To: Christoph Paasch <cpaasch@...le.com>
Cc: Yuchung Cheng <ycheng@...gle.com>,
David Miller <davem@...emloft.net>,
netdev <netdev@...r.kernel.org>,
Neal Cardwell <ncardwell@...gle.com>,
"maheshb@...gle.com" <maheshb@...gle.com>
Subject: Re: [PATCH net-next] tcp: socket option to set TCP fast open key
On Wed, Oct 18, 2017 at 1:13 PM, Christoph Paasch <cpaasch@...le.com> wrote:
>
> Hello Yuchung,
>
> On 18/10/17 - 11:22:51, Yuchung Cheng wrote:
> > New socket option TCP_FASTOPEN_KEY to allow different keys per
> > listener. The listener by default uses the global key until the
> > socket option is set. The key is a 16 bytes long binary data. This
> > option has no effect on regular non-listener TCP sockets.
>
> can you explain what the use-case is to have per-listener TFO keys?
>
Security aspects. You want to be able to change keys whenever you
want, on an application basis.
Powered by blists - more mailing lists