[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFLxGvysjYbCpkqbVqD8Q1v3isGnRrNo5KdUn7TgCVt9WxzE2g@mail.gmail.com>
Date: Tue, 5 Jun 2018 17:13:35 +0200
From: Richard Weinberger <richard.weinberger@...il.com>
To: "Theodore Y. Ts'o" <tytso@....edu>,
Linus Torvalds <torvalds@...ux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>,
linux-fscrypt@...r.kernel.org
Subject: Re: [GIT PULL] fscrypt updates for 4.18
Ted,
On Tue, Jun 5, 2018 at 5:07 PM, Theodore Y. Ts'o <tytso@....edu> wrote:
> The following changes since commit 75bc37fefc4471e718ba8e651aa74673d4e0a9eb:
>
> Linux 4.17-rc4 (2018-05-06 16:57:38 -1000)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tytso/fscrypt.git tags/fscrypt_for_linus
>
> for you to fetch changes up to 4f2f76f751433908364ccff82f437a57d0e6e9b7:
>
> ext4: fix fencepost error in check for inode count overflow during resize (2018-05-25 12:51:25 -0400)
>
> ----------------------------------------------------------------
> Add bunch of cleanups, and add support for the Speck128/256
> algorithms. Yes, Speck is contrversial, but the intention is to use
> them only for the lowest end Android devices, where the alternative
> *really* is no encryption at all for data stored at rest.
Will Android tell me that Speck is being used?
--
Thanks,
//richard
Powered by blists - more mailing lists