From: Stephan Mueller <smueller@chronox.de>
Subject: Re: a few questions on AF_ALG specification (AEAD, socket/connection, ...)
Date: Mon, 01 Aug 2016 11:27:42 +0200
Message-ID: <3728111.m6YveIaSmG@tauon.atsec.com>
References: <57974E05.3030502@kalray.eu> <429e56bc-4ae9-a682-63a4-b34a38295abc@intel.com> <706562074.101482886.1470042847657.JavaMail.zimbra@kalray.eu>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8BIT
Cc: Tadeusz Struk <tadeusz.struk@intel.com>,
	Linux Crypto Mailing List <linux-crypto@vger.kernel.org>
To: Nicolas Brunie <nbrunie@kalray.eu>
In-Reply-To: <706562074.101482886.1470042847657.JavaMail.zimbra@kalray.eu>
Sender: linux-crypto-owner@vger.kernel.org

Am Montag, 1. August 2016, 11:14:07 CEST schrieb Nicolas Brunie:

Hi Nicolas,

> Hi,
>   In my understanding, a socket is the file descriptor given as argument to
> a bind call and a connection is the file descriptor returned by an accept
> call.

This would be an appropriate naming:

The key is set on a socket. The IV is given with the connection.

> 
> NB
> 
> 
> 
> ----- Mail original -----
> De: "Tadeusz Struk" <tadeusz.struk@intel.com>
> ?: "Stephan Mueller" <smueller@chronox.de>, "Nicolas Brunie"
> <nicolas.brunie@kalray.eu> Cc: "Linux Crypto Mailing List"
> <linux-crypto@vger.kernel.org>
> Envoy?: Mardi 26 Juillet 2016 16:37:51
> Objet: Re: a few questions on AF_ALG specification (AEAD, socket/
connection,
> ...)
> 
> Hi,
> 
> On 07/26/2016 04:54 AM, Stephan Mueller wrote:
> >> > Is it true that the key (defined via setsockopt) is common to all the
> >> > connections but the IV (defined through message control header) is
> >> > specific to each connection ?
> > 
> > Yes.
> 
> I think that's not correct. Please define a "connection".
> If you think of connections as separate sockets, then you can
> have different keys for each socket. The difference is that
> you set a key per each socket once, and you send IV for each
> operation (encrypt/decrypt).
> Thanks,


Ciao
Stephan