[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1a2e01d595ee$23eae790$6bc0b6b0$@dektech.com.au>
Date: Fri, 8 Nov 2019 11:36:49 +0700
From: "Tuong Lien Tong" <tuong.t.lien@...tech.com.au>
To: "'David Miller'" <davem@...emloft.net>
Cc: <jon.maloy@...csson.com>, <maloy@...jonn.com>,
<ying.xue@...driver.com>, <netdev@...r.kernel.org>,
<tipc-discussion@...ts.sourceforge.net>
Subject: RE: [net-next 0/5] TIPC encryption
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@...emloft.net>
Sent: Friday, November 8, 2019 11:07 AM
To: tuong.t.lien@...tech.com.au
Cc: jon.maloy@...csson.com; maloy@...jonn.com; ying.xue@...driver.com;
netdev@...r.kernel.org; tipc-discussion@...ts.sourceforge.net
Subject: Re: [net-next 0/5] TIPC encryption
From: Tuong Lien <tuong.t.lien@...tech.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.
Powered by blists - more mailing lists