Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Stephan Mueller <smueller@chronox.de>
To: Nicolas Brunie <nbrunie@kalray.eu>
Cc: Tadeusz Struk <tadeusz.struk@intel.com>,
	Linux Crypto Mailing List <linux-crypto@vger.kernel.org>
Subject: Re: a few questions on AF_ALG specification (AEAD, socket/connection, ...)
Date: Mon, 01 Aug 2016 11:27:42 +0200	[thread overview]
Message-ID: <3728111.m6YveIaSmG@tauon.atsec.com> (raw)
In-Reply-To: <706562074.101482886.1470042847657.JavaMail.zimbra@kalray.eu>

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

      reply	other threads:[~2016-08-01  9:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-26 11:48 a few questions on AF_ALG specification (AEAD, socket/connection, ...) Nicolas Brunie
2016-07-26 11:54 ` Stephan Mueller
2016-07-26 14:37   ` Tadeusz Struk
2016-08-01  9:14     ` Nicolas Brunie
2016-08-01  9:27       ` Stephan Mueller [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3728111.m6YveIaSmG@tauon.atsec.com \
    --to=smueller@chronox.de \
    --cc=linux-crypto@vger.kernel.org \
    --cc=nbrunie@kalray.eu \
    --cc=tadeusz.struk@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox