Linux-FSCrypt Archive on
 help / color / Atom feed
From: Omar Sandoval <>
Cc: Sergey Anpilov <>, Pavlo Kushnir <>
Subject: Using TPM trusted keys (w/ v2 policies?)
Date: Thu, 16 Jan 2020 11:32:28 -0800
Message-ID: <20200116193228.GA266386@vader> (raw)


We're exploring fscrypt, and we were hoping to make use of a trusted key [1] so
that we could avoid exposing the master key to userspace. I found a patch [2]
from a couple of years ago adding this support. However, trusted keys in the
kernel seem to be tied to the keyring, which is not used for v2 encryption
policies. Seeing as v1 policies are considered deprecated, what would be the
way to move forward with this feature? Would it make sense to add minimal
keyring integration for v2 policies in order to support this use case?



             reply index

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-16 19:32 Omar Sandoval [this message]
2020-01-16 19:53 ` 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:

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

  git send-email \
    --in-reply-to=20200116193228.GA266386@vader \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-FSCrypt Archive on

Archives are clonable:
	git clone --mirror linux-fscrypt/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-fscrypt linux-fscrypt/ \
	public-inbox-index linux-fscrypt

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone