All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] some questions on dm-crypt/cryptsetup and LUKS2+integrity
Date: Tue, 4 Sep 2018 17:53:53 +0200	[thread overview]
Message-ID: <20180904155353.GA13223@tansi.org> (raw)
In-Reply-To: <4dfe02059c02f38381ab16ee5b96716fe46cf51a.camel@scientia.net>

On Tue, Sep 04, 2018 at 14:49:29 CEST, Christoph Anton Mitterer wrote:
> On Mon, 2018-09-03 at 09:48 +0200, Milan Broz wrote:
> > sorry for long delay, I was most of the time offline.
> Thanks, and no worries :-)
> 
> 
> > On 19/08/18 19:27, Christoph Anton Mitterer wrote:
> > > - ChaCha20 seems to have all 128 bit IV... but is this correct?
> > > I've
> > >   modpobed chacha20poly1305 ... but at least ther's no reference to
> > >   poly1305 in /proc/crypto
> > 
> > No, we use RFC7539 wrapper for Chacha20-poly1305 and here the nonce
> > is
> > only 96bit.
> > 
> > So the same probability of collision as in GCM, just a nonce
> > collision
> > does not cause such fatal failure as in GCM.
> 
> Are there any plans to provide ChaCha20/Poly1305 with larger nonces in
> the future?

I don't think that is a concern. 96bit, even if randomly chosen, 
is unlikely to collide in the remaining lifetime of this star-system.

Regards,
Arno

-- 
Arno Wagner,     Dr. sc. techn., Dipl. Inform.,    Email: arno@wagner.name
GnuPG: ID: CB5D9718  FP: 12D6 C03B 1B30 33BB 13CF  B774 E35C 5FA1 CB5D 9718
----
A good decision is based on knowledge and not on numbers. -- Plato

If it's in the news, don't worry about it.  The very definition of 
"news" is "something that hardly ever happens." -- Bruce Schneier

  reply	other threads:[~2018-09-04 15:53 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-16 15:52 [dm-crypt] some questions on dm-crypt/cryptsetup and LUKS2+integrity Christoph Anton Mitterer
2018-08-17 12:23 ` Milan Broz
2018-08-17 13:26   ` Christoph Anton Mitterer
2018-08-19 10:07     ` Milan Broz
2018-08-19 17:27       ` Christoph Anton Mitterer
2018-09-03  7:48         ` Milan Broz
2018-09-04 12:49           ` Christoph Anton Mitterer
2018-09-04 15:53             ` Arno Wagner [this message]
2018-09-04 17:14               ` Milan Broz
2018-10-15 15:11                 ` Christoph Anton Mitterer
2018-10-16  7:10                   ` Milan Broz
2018-11-19 21:03                     ` Christoph Anton Mitterer
2018-11-20 10:08                       ` Ondrej Kozina
2018-11-20 13:57                         ` Christoph Anton Mitterer
2018-11-20 16:05                           ` Milan Broz
2018-11-20 17:07                             ` Christoph Anton Mitterer
2018-11-20 17:54                               ` Milan Broz
2019-01-14  5:48                                 ` Christoph Anton Mitterer

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=20180904155353.GA13223@tansi.org \
    --to=arno@wagner.name \
    --cc=dm-crypt@saout.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.