From: David Ahern <dsahern@gmail.com>
To: Tuong Lien <tuong.t.lien@dektech.com.au>,
jon.maloy@ericsson.com, maloy@donjonn.com,
ying.xue@windriver.com, netdev@vger.kernel.org
Cc: tipc-discussion@lists.sourceforge.net
Subject: Re: [iproute2-next] tipc: add new commands to set TIPC AEAD key
Date: Mon, 25 Nov 2019 16:16:23 -0700 [thread overview]
Message-ID: <f10b8f69-e9d8-e69d-3c28-f73f37007cd5@gmail.com> (raw)
In-Reply-To: <20191121034646.16737-1-tuong.t.lien@dektech.com.au>
On 11/20/19 8:46 PM, Tuong Lien wrote:
> Two new commands are added as part of 'tipc node' command:
>
> $tipc node set key KEY [algname ALGNAME] [nodeid NODEID]
> $tipc node flush key
>
> which enable user to set and remove AEAD keys in kernel TIPC (requires
> the kernel option - 'TIPC_CRYPTO').
>
> For the 'set key' command, the given 'nodeid' parameter decides the
> mode to be applied to the key, particularly:
>
> - If NODEID is empty, the key is a 'cluster' key which will be used for
> all message encryption/decryption from/to the node (i.e. both TX & RX).
> The same key will be set in the other nodes.
>
> - If NODEID is own node, the key is used for message encryption (TX)
> from the node. Whereas, if NODEID is a peer node, the key is for
> message decryption (RX) from that peer node. This is the 'per-node-key'
> mode that each nodes in the cluster has its specific (TX) key.
>
> Acked-by: Ying Xue <ying.xue@windriver.com>
> Acked-by: Jon Maloy <jon.maloy@ericsson.com>
> Signed-off-by: Tuong Lien <tuong.t.lien@dektech.com.au>
> ---
> include/uapi/linux/tipc.h | 21 ++++++
> include/uapi/linux/tipc_netlink.h | 4 ++
> tipc/misc.c | 38 +++++++++++
> tipc/misc.h | 1 +
> tipc/node.c | 133 +++++++++++++++++++++++++++++++++++++-
> 5 files changed, 195 insertions(+), 2 deletions(-)
>
applied to iproute2-next. Thanks
prev parent reply other threads:[~2019-11-25 23:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-21 3:46 [iproute2-next] tipc: add new commands to set TIPC AEAD key Tuong Lien
2019-11-25 23:16 ` David Ahern [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=f10b8f69-e9d8-e69d-3c28-f73f37007cd5@gmail.com \
--to=dsahern@gmail.com \
--cc=jon.maloy@ericsson.com \
--cc=maloy@donjonn.com \
--cc=netdev@vger.kernel.org \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=tuong.t.lien@dektech.com.au \
--cc=ying.xue@windriver.com \
/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).