Message ID | 20191108014213.32219-1-tuong.t.lien@dektech.com.au |
---|---|
Headers | show |
Series | TIPC encryption | expand |
From: Tuong Lien <tuong.t.lien@dektech.com.au> Date: Fri, 8 Nov 2019 08:42:08 +0700 > This series provides TIPC encryption feature, kernel part. There will be > another one in the 'iproute2/tipc' for user space to set key. If gcm(aes) is the only algorithm you accept, you will need to express this dependency in the Kconfig file. Otherwise it is pointless to turn on the TIPC crypto Kconfig option.
You are right, David. I am going to resend the v2 series with an update for it. Thanks/Tuong -----Original Message----- From: David Miller <davem@davemloft.net> Sent: Friday, November 8, 2019 11:07 AM To: tuong.t.lien@dektech.com.au Cc: jon.maloy@ericsson.com; maloy@donjonn.com; ying.xue@windriver.com; netdev@vger.kernel.org; tipc-discussion@lists.sourceforge.net Subject: Re: [net-next 0/5] TIPC encryption From: Tuong Lien <tuong.t.lien@dektech.com.au> Date: Fri, 8 Nov 2019 08:42:08 +0700 > This series provides TIPC encryption feature, kernel part. There will be > another one in the 'iproute2/tipc' for user space to set key. If gcm(aes) is the only algorithm you accept, you will need to express this dependency in the Kconfig file. Otherwise it is pointless to turn on the TIPC crypto Kconfig option.