From: Eric Dumazet <eric.dumazet@gmail.com>
To: Ivan Delalande <colona@arista.com>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v5 2/2] tcp_diag: report TCP MD5 signing keys and addresses
Date: Thu, 31 Aug 2017 19:58:49 -0700 [thread overview]
Message-ID: <1504234729.15310.20.camel@edumazet-glaptop3.roam.corp.google.com> (raw)
In-Reply-To: <20170831165939.5121-3-colona@arista.com>
On Thu, 2017-08-31 at 09:59 -0700, Ivan Delalande wrote:
> Report TCP MD5 (RFC2385) signing keys, addresses and address prefixes to
> processes with CAP_NET_ADMIN requesting INET_DIAG_INFO. Currently it is
> not possible to retrieve these from the kernel once they have been
> configured on sockets.
>
> Signed-off-by: Ivan Delalande <colona@arista.com>
> ---
> include/uapi/linux/inet_diag.h | 1 +
> include/uapi/linux/tcp.h | 9 ++++
> net/ipv4/tcp_diag.c | 109 ++++++++++++++++++++++++++++++++++++++---
> 3 files changed, 113 insertions(+), 6 deletions(-)
Acked-by: Eric Dumazet <edumazet@google.com>
next prev parent reply other threads:[~2017-09-01 2:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-31 16:59 [PATCH net-next v5 0/2] report TCP MD5 signing keys and addresses Ivan Delalande
2017-08-31 16:59 ` [PATCH net-next v5 1/2] inet_diag: allow protocols to provide additional data Ivan Delalande
2017-09-01 2:57 ` Eric Dumazet
2017-08-31 16:59 ` [PATCH net-next v5 2/2] tcp_diag: report TCP MD5 signing keys and addresses Ivan Delalande
2017-08-31 23:26 ` Sabrina Dubroca
2017-09-01 0:21 ` Ivan Delalande
2017-09-01 15:47 ` Sabrina Dubroca
2017-09-01 2:58 ` Eric Dumazet [this message]
2017-09-02 1:38 ` [PATCH net-next v5 0/2] " David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1504234729.15310.20.camel@edumazet-glaptop3.roam.corp.google.com \
--to=eric.dumazet@gmail.com \
--cc=colona@arista.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox