From: Eric Biggers <ebiggers@kernel.org> To: fstests@vger.kernel.org Cc: linux-fscrypt@vger.kernel.org, keyrings@vger.kernel.org, Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com> Subject: [RFC PATCH 0/3] xfstests: test adding filesystem-level fscrypt key via key_id Date: Tue, 19 Nov 2019 14:31:27 -0800 [thread overview] Message-ID: <20191119223130.228341-1-ebiggers@kernel.org> (raw) This series adds a test which tests adding a key to a filesystem's fscrypt keyring via an "fscrypt-provisioning" keyring key. This is an alternative to the normal method where the raw key is given directly. I'm sending this out for comment, but it shouldn't be merged until the corresponding kernel patch has reached mainline. For more details, see the kernel patch: https://lkml.kernel.org/linux-fscrypt/20191119222447.226853-1-ebiggers@kernel.org/T/#u This test depends on an xfs_io patch which adds the '-k' option to the 'add_enckey' command, e.g.: xfs_io -c "add_enckey -k KEY_ID" MOUNTPOINT This test is skipped if the needed kernel or xfs_io support is absent. This has been tested on ext4, f2fs, and ubifs. To apply cleanly, my other xfstests patch series "[RFC PATCH 0/5] xfstests: verify ciphertext of IV_INO_LBLK_64 encryption policies" must be applied first. This series can also be retrieved from https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/xfstests-dev.git tag "fscrypt-provisioning_2019-11-19". Eric Biggers (3): common/rc: handle option with argument in _require_xfs_io_command() common/encrypt: move constant test key to common code generic: test adding filesystem-level fscrypt key via key_id common/encrypt | 95 +++++++++++++++++++++---- common/rc | 2 +- tests/generic/580 | 17 ++--- tests/generic/806 | 156 ++++++++++++++++++++++++++++++++++++++++++ tests/generic/806.out | 73 ++++++++++++++++++++ tests/generic/group | 1 + 6 files changed, 316 insertions(+), 28 deletions(-) create mode 100644 tests/generic/806 create mode 100644 tests/generic/806.out -- 2.24.0.432.g9d3f5f5b63-goog
WARNING: multiple messages have this Message-ID (diff)
From: Eric Biggers <ebiggers@kernel.org> To: fstests@vger.kernel.org Cc: linux-fscrypt@vger.kernel.org, keyrings@vger.kernel.org, Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com> Subject: [RFC PATCH 0/3] xfstests: test adding filesystem-level fscrypt key via key_id Date: Tue, 19 Nov 2019 22:31:27 +0000 [thread overview] Message-ID: <20191119223130.228341-1-ebiggers@kernel.org> (raw) This series adds a test which tests adding a key to a filesystem's fscrypt keyring via an "fscrypt-provisioning" keyring key. This is an alternative to the normal method where the raw key is given directly. I'm sending this out for comment, but it shouldn't be merged until the corresponding kernel patch has reached mainline. For more details, see the kernel patch: https://lkml.kernel.org/linux-fscrypt/20191119222447.226853-1-ebiggers@kernel.org/T/#u This test depends on an xfs_io patch which adds the '-k' option to the 'add_enckey' command, e.g.: xfs_io -c "add_enckey -k KEY_ID" MOUNTPOINT This test is skipped if the needed kernel or xfs_io support is absent. This has been tested on ext4, f2fs, and ubifs. To apply cleanly, my other xfstests patch series "[RFC PATCH 0/5] xfstests: verify ciphertext of IV_INO_LBLK_64 encryption policies" must be applied first. This series can also be retrieved from https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/xfstests-dev.git tag "fscrypt-provisioning_2019-11-19". Eric Biggers (3): common/rc: handle option with argument in _require_xfs_io_command() common/encrypt: move constant test key to common code generic: test adding filesystem-level fscrypt key via key_id common/encrypt | 95 +++++++++++++++++++++---- common/rc | 2 +- tests/generic/580 | 17 ++--- tests/generic/806 | 156 ++++++++++++++++++++++++++++++++++++++++++ tests/generic/806.out | 73 ++++++++++++++++++++ tests/generic/group | 1 + 6 files changed, 316 insertions(+), 28 deletions(-) create mode 100644 tests/generic/806 create mode 100644 tests/generic/806.out -- 2.24.0.432.g9d3f5f5b63-goog
next reply other threads:[~2019-11-19 22:32 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-11-19 22:31 Eric Biggers [this message] 2019-11-19 22:31 ` [RFC PATCH 0/3] xfstests: test adding filesystem-level fscrypt key via key_id Eric Biggers 2019-11-19 22:31 ` [RFC PATCH 1/3] common/rc: handle option with argument in _require_xfs_io_command() Eric Biggers 2019-11-19 22:31 ` Eric Biggers 2019-11-19 22:31 ` [RFC PATCH 2/3] common/encrypt: move constant test key to common code Eric Biggers 2019-11-19 22:31 ` Eric Biggers 2019-11-19 22:31 ` [RFC PATCH 3/3] generic: test adding filesystem-level fscrypt key via key_id Eric Biggers 2019-11-19 22:31 ` Eric Biggers 2019-11-21 0:25 ` Eric Biggers 2019-11-21 0:25 ` Eric Biggers 2019-11-27 20:45 ` [RFC PATCH 0/3] xfstests: " Jarkko Sakkinen 2019-11-27 20:45 ` Jarkko Sakkinen 2019-11-27 20:46 ` Jarkko Sakkinen 2019-11-27 20:46 ` Jarkko Sakkinen 2019-11-27 22:57 ` Eric Biggers 2019-11-27 22:57 ` Eric Biggers 2019-12-11 9:50 ` Jarkko Sakkinen 2019-12-11 9:50 ` Jarkko Sakkinen 2019-12-11 18:00 ` Eric Biggers 2019-12-11 18:00 ` 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=20191119223130.228341-1-ebiggers@kernel.org \ --to=ebiggers@kernel.org \ --cc=fstests@vger.kernel.org \ --cc=jarkko.sakkinen@linux.intel.com \ --cc=keyrings@vger.kernel.org \ --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: linkBe 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.