mirror of
https://github.com/edk2-porting/linux-next.git
synced 2024-12-23 04:34:11 +08:00
fc1b6d6de2
This commit offers an option to encrypt and authenticate all messaging,
including the neighbor discovery messages. The currently most advanced
algorithm supported is the AEAD AES-GCM (like IPSec or TLS). All
encryption/decryption is done at the bearer layer, just before leaving
or after entering TIPC.
Supported features:
- Encryption & authentication of all TIPC messages (header + data);
- Two symmetric-key modes: Cluster and Per-node;
- Automatic key switching;
- Key-expired revoking (sequence number wrapped);
- Lock-free encryption/decryption (RCU);
- Asynchronous crypto, Intel AES-NI supported;
- Multiple cipher transforms;
- Logs & statistics;
Two key modes:
- Cluster key mode: One single key is used for both TX & RX in all
nodes in the cluster.
- Per-node key mode: Each nodes in the cluster has one specific TX key.
For RX, a node requires its peers' TX key to be able to decrypt the
messages from those peers.
Key setting from user-space is performed via netlink by a user program
(e.g. the iproute2 'tipc' tool).
Internal key state machine:
Attach Align(RX)
+-+ +-+
| V | V
+---------+ Attach +---------+
| IDLE |---------------->| PENDING |(user = 0)
+---------+ +---------+
A A Switch| A
| | | |
| | Free(switch/revoked) | |
(Free)| +----------------------+ | |Timeout
| (TX) | | |(RX)
| | | |
| | v |
+---------+ Switch +---------+
| PASSIVE |<----------------| ACTIVE |
+---------+ (RX) +---------+
(user = 1) (user >= 1)
The number of TFMs is 10 by default and can be changed via the procfs
'net/tipc/max_tfms'. At this moment, as for simplicity, this file is
also used to print the crypto statistics at runtime:
echo 0xfff1 > /proc/sys/net/tipc/max_tfms
The patch defines a new TIPC version (v7) for the encryption message (-
backward compatibility as well). The message is basically encapsulated
as follows:
+----------------------------------------------------------+
| TIPCv7 encryption | Original TIPCv2 | Authentication |
| header | packet (encrypted) | Tag |
+----------------------------------------------------------+
The throughput is about ~40% for small messages (compared with non-
encryption) and ~9% for large messages. With the support from hardware
crypto i.e. the Intel AES-NI CPU instructions, the throughput increases
upto ~85% for small messages and ~55% for large messages.
By default, the new feature is inactive (i.e. no encryption) until user
sets a key for TIPC. There is however also a new option - "TIPC_CRYPTO"
in the kernel configuration to enable/disable the new code when needed.
MAINTAINERS | add two new files 'crypto.h' & 'crypto.c' in tipc
Acked-by: Ying Xue <ying.xue@windreiver.com>
Acked-by: Jon Maloy <jon.maloy@ericsson.com>
Signed-off-by: Tuong Lien <tuong.t.lien@dektech.com.au>
Signed-off-by: David S. Miller <davem@davemloft.net>
61 lines
1.8 KiB
Plaintext
61 lines
1.8 KiB
Plaintext
# SPDX-License-Identifier: GPL-2.0-only
|
|
#
|
|
# TIPC configuration
|
|
#
|
|
|
|
menuconfig TIPC
|
|
tristate "The TIPC Protocol"
|
|
depends on INET
|
|
---help---
|
|
The Transparent Inter Process Communication (TIPC) protocol is
|
|
specially designed for intra cluster communication. This protocol
|
|
originates from Ericsson where it has been used in carrier grade
|
|
cluster applications for many years.
|
|
|
|
For more information about TIPC, see http://tipc.sourceforge.net.
|
|
|
|
This protocol support is also available as a module ( = code which
|
|
can be inserted in and removed from the running kernel whenever you
|
|
want). The module will be called tipc. If you want to compile it
|
|
as a module, say M here and read <file:Documentation/kbuild/modules.rst>.
|
|
|
|
If in doubt, say N.
|
|
|
|
config TIPC_MEDIA_IB
|
|
bool "InfiniBand media type support"
|
|
depends on TIPC && INFINIBAND_IPOIB
|
|
help
|
|
Saying Y here will enable support for running TIPC on
|
|
IP-over-InfiniBand devices.
|
|
config TIPC_MEDIA_UDP
|
|
bool "IP/UDP media type support"
|
|
depends on TIPC
|
|
select NET_UDP_TUNNEL
|
|
help
|
|
Saying Y here will enable support for running TIPC over IP/UDP
|
|
bool
|
|
default y
|
|
config TIPC_CRYPTO
|
|
bool "TIPC encryption support"
|
|
depends on TIPC
|
|
select CRYPTO
|
|
select CRYPTO_AES
|
|
select CRYPTO_GCM
|
|
help
|
|
Saying Y here will enable support for TIPC encryption.
|
|
All TIPC messages will be encrypted/decrypted by using the currently most
|
|
advanced algorithm: AEAD AES-GCM (like IPSec or TLS) before leaving/
|
|
entering the TIPC stack.
|
|
Key setting from user-space is performed via netlink by a user program
|
|
(e.g. the iproute2 'tipc' tool).
|
|
bool
|
|
default y
|
|
|
|
config TIPC_DIAG
|
|
tristate "TIPC: socket monitoring interface"
|
|
depends on TIPC
|
|
default y
|
|
---help---
|
|
Support for TIPC socket monitoring interface used by ss tool.
|
|
If unsure, say Y.
|