From: Stephen Hemminger <stephen@networkplumber.org>
To: Ivan Delalande <colona@arista.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH iproute2 2/2] ss: print MD5 signature keys configured on TCP sockets
Date: Wed, 11 Oct 2017 11:06:54 -0700 [thread overview]
Message-ID: <20171011110654.260f9b8c@xeon-e3> (raw)
In-Reply-To: <20171006234820.27567-2-colona@arista.com>
On Fri, 6 Oct 2017 16:48:20 -0700
Ivan Delalande <colona@arista.com> wrote:
> These keys are reported by kernel 4.14 and later under the
> INET_DIAG_MD5SIG attribute, when INET_DIAG_INFO is requested (ss -i)
> and we have CAP_NET_ADMIN. The additional output looks like:
>
> md5keys:fe80::/64=signing_key,10.1.2.0/24=foobar,::1/128=Test
>
> Signed-off-by: Ivan Delalande <colona@arista.com>
Sure makes sense applied.
prev parent reply other threads:[~2017-10-11 18:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-06 23:48 [PATCH iproute2 1/2] utils: add print_escape_buf to format and print arbitrary bytes Ivan Delalande
2017-10-06 23:48 ` [PATCH iproute2 2/2] ss: print MD5 signature keys configured on TCP sockets Ivan Delalande
2017-10-11 18:06 ` Stephen Hemminger [this message]
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=20171011110654.260f9b8c@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=colona@arista.com \
--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;
as well as URLs for NNTP newsgroup(s).