linux-fscrypt.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Richard Weinberger <richard@sigma-star.at>
Cc: Richard Weinberger <richard.weinberger@gmail.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-fscrypt@vger.kernel.org
Subject: Re: [GIT PULL] fscrypt updates for 4.18
Date: Tue, 5 Jun 2018 17:12:38 -0400	[thread overview]
Message-ID: <20180605211238.GH7839@thunk.org> (raw)
In-Reply-To: <5151941.CDXohbuWeC@blindfold>

On Tue, Jun 05, 2018 at 07:05:52PM +0200, Richard Weinberger wrote:
> > An attack scenario where someone manages to downgrade the crypto of
> > your phone would require replacing your kernel and your /system
> > partition --- at which point, you've got other problems.  :-)
> 
> This means Speck is never enabled at kernel level on non-cheap phones?

No.  And even if it were, the /system partition is going to request
that the kernel encrypt files using one and only encryption algorithm:
namely, AES.

Things aren't as configurable on an Android phone as you might be used
to on a laptop.  Some manufacturers use ext4; some manufacturers
decide they want to use f2fs.  They make that decision not you, and
only the file system utilities for that one file system are compiled
into the system.

Similarly, you don't get to choose what crypto algorithm you use;
that's decided for you by the manufacturer.  Which is good; it's one
less thing that hte attacker can spoof, and one less thing for users
to potentially get wrong.

					- Ted

  reply	other threads:[~2018-06-05 21:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-05 15:07 [GIT PULL] fscrypt updates for 4.18 Theodore Y. Ts'o
2018-06-05 15:13 ` Richard Weinberger
2018-06-05 15:35   ` Theodore Y. Ts'o
2018-06-05 16:10     ` Richard Weinberger
2018-06-05 17:02       ` Theodore Y. Ts'o
2018-06-05 17:05         ` Richard Weinberger
2018-06-05 21:12           ` Theodore Y. Ts'o [this message]
2018-06-05 20:22 ` Linus Torvalds
2018-06-05 22:12   ` Theodore Y. Ts'o

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=20180605211238.GH7839@thunk.org \
    --to=tytso@mit.edu \
    --cc=linux-fscrypt@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richard.weinberger@gmail.com \
    --cc=richard@sigma-star.at \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).