Re: [PATCH net-next] net/tls: Add support of AES128-CCM based ciphers

2019-03-19 Thread David Miller
From: Vakul Garg Date: Tue, 19 Mar 2019 05:15:20 + > @@ -479,11 +477,18 @@ static int tls_do_encryption(struct sock *sk, > struct tls_rec *rec = ctx->open_rec; > struct sk_msg *msg_en = &rec->msg_encrypted; > struct scatterlist *sge = sk_msg_elem(msg_en, start); > - int

RE: [PATCH net-next] net/tls: Add support of AES128-CCM based ciphers

2019-03-19 Thread Vakul Garg
> -Original Message- > From: Boris Pismenny > Sent: Tuesday, March 19, 2019 10:36 PM > To: Vakul Garg ; netdev@vger.kernel.org > Cc: Aviad Yehezkel ; davejwat...@fb.com; > da...@davemloft.net; doro...@fb.com > Subject: Re: [PATCH net-next] net/tls: Add suppor

Re: [PATCH net-next] net/tls: Add support of AES128-CCM based ciphers

2019-03-19 Thread Boris Pismenny
On 3/19/2019 7:15 AM, Vakul Garg wrote: > Added support for AES128-CCM based record encryption. AES128-CCM is > similar to AES128-GCM. Both of them have same salt/iv/mac size. The > notable difference between the two is that while invoking AES128-CCM > operation, the salt||nonce (which is passed a

[PATCH net-next] net/tls: Add support of AES128-CCM based ciphers

2019-03-18 Thread Vakul Garg
Added support for AES128-CCM based record encryption. AES128-CCM is similar to AES128-GCM. Both of them have same salt/iv/mac size. The notable difference between the two is that while invoking AES128-CCM operation, the salt||nonce (which is passed as IV) has to be prefixed with a hardcoded value '