Linux-FSCrypt Archive on
 help / color / Atom feed
* Using TPM trusted keys (w/ v2 policies?)
@ 2020-01-16 19:32 Omar Sandoval
  2020-01-16 19:53 ` Eric Biggers
  0 siblings, 1 reply; 2+ messages in thread
From: Omar Sandoval @ 2020-01-16 19:32 UTC (permalink / raw)
  To: linux-fscrypt; +Cc: Sergey Anpilov, Pavlo Kushnir


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?



^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, back to index

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-01-16 19:32 Using TPM trusted keys (w/ v2 policies?) Omar Sandoval
2020-01-16 19:53 ` Eric Biggers

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