All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geo Kozey <geokozey@mailfence.com>
To: Eric Biggers <ebiggers3@gmail.com>
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>,
	linux-fscrypt@vger.kernel.org,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	ebiggers@google.com
Subject: Re: [PATCH] fscrypt: add support for ChaCha20 contents encryption
Date: Sat, 9 Dec 2017 16:40:56 +0100 (CET)	[thread overview]
Message-ID: <483722360.123210.1512834056036@ichabod.co-bxl> (raw)
In-Reply-To: <20171208214213.GA104193@gmail.com>

> From: Eric Biggers <ebiggers3@gmail.com>
> Sent: Fri Dec 08 22:42:13 CET 2017
> Subject: Re: [PATCH] fscrypt: add support for ChaCha20 contents encryption
> 
> We can't use authenticated encryption for the same reason we can't use random or
> sequential nonces: there is nowhere to store the additional metadata
> (authentication tag and nonce) per filesystem block *and* have it updated
> atomically with respect to the contents of said block. 

I saw that LUKS/dm-crypt guys are able to do AE regardless of the same issues[1].
Is it really impossible for fscrypt?

[1] http://www.saout.de/pipermail/dm-crypt/2017-November/005745.html

Yours sincerely

G. K.

  reply	other threads:[~2017-12-09 15:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-08  1:38 [PATCH] fscrypt: add support for ChaCha20 contents encryption Eric Biggers
2017-12-08  2:51 ` Jason A. Donenfeld
2017-12-08  7:20   ` Ard Biesheuvel
2017-12-08 21:42     ` Eric Biggers
2017-12-09 15:40       ` Geo Kozey [this message]
2017-12-10 19:05         ` Eric Biggers
2017-12-11 16:11   ` David Gstir
2017-12-08  9:11 ` Ard Biesheuvel
2017-12-08  9:11   ` Ard Biesheuvel
2017-12-08 10:06     ` Ard Biesheuvel
2017-12-08 10:06       ` Ard Biesheuvel
2017-12-08 10:14       ` Stephan Mueller
2017-12-08 10:27         ` Ard Biesheuvel
2017-12-08 10:27           ` Ard Biesheuvel
2017-12-09  0:48 ` Jeffrey Walton
2017-12-10 18:59   ` Eric Biggers

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=483722360.123210.1512834056036@ichabod.co-bxl \
    --to=geokozey@mailfence.com \
    --cc=Jason@zx2c4.com \
    --cc=ard.biesheuvel@linaro.org \
    --cc=ebiggers3@gmail.com \
    --cc=ebiggers@google.com \
    --cc=linux-fscrypt@vger.kernel.org \
    /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.