From: Eric Biggers <ebiggers@kernel.org>
To: fstests@vger.kernel.org
Cc: linux-fscrypt@vger.kernel.org
Subject: [PATCH v2 4/5] common/encrypt: log full ciphertext verification params
Date: Sat, 12 Mar 2022 17:05:58 -0800 [thread overview]
Message-ID: <20220313010559.545995-5-ebiggers@kernel.org> (raw)
In-Reply-To: <20220313010559.545995-1-ebiggers@kernel.org>
From: Eric Biggers <ebiggers@google.com>
To help with debugging, log some additional information to $seqres.full.
Signed-off-by: Eric Biggers <ebiggers@google.com>
---
common/encrypt | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/common/encrypt b/common/encrypt
index 2cf02ca0..cf402570 100644
--- a/common/encrypt
+++ b/common/encrypt
@@ -908,6 +908,17 @@ _verify_ciphertext_for_encryption_policy()
echo -e "\tfilenames_encryption_mode: $filenames_encryption_mode"
[ $# -ne 0 ] && echo -e "\toptions: $*"
+ cat >> $seqres.full <<EOF
+Full ciphertext verification parameters:
+ contents_encryption_mode = $contents_encryption_mode
+ filenames_encryption_mode = $filenames_encryption_mode
+ policy_flags = $policy_flags
+ set_encpolicy_args = $set_encpolicy_args
+ keyspec = $keyspec
+ raw_key_hex = $raw_key_hex
+ crypt_util_contents_args = $crypt_util_contents_args
+ crypt_util_filename_args = $crypt_util_filename_args
+EOF
_do_verify_ciphertext_for_encryption_policy \
"$contents_encryption_mode" \
"$filenames_encryption_mode" \
--
2.35.1
next prev parent reply other threads:[~2022-03-13 1:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-13 1:05 [PATCH v2 0/5] xfstests: fscrypt test cleanups Eric Biggers
2022-03-13 1:05 ` [PATCH v2 1/5] fscrypt-crypt-util: use an explicit --direct-key option Eric Biggers
2022-03-13 1:05 ` [PATCH v2 2/5] fscrypt-crypt-util: refactor get_key_and_iv() Eric Biggers
2022-03-13 1:05 ` [PATCH v2 3/5] fscrypt-crypt-util: add support for dumping key identifier Eric Biggers
2022-03-13 1:05 ` Eric Biggers [this message]
2022-03-13 1:05 ` [PATCH v2 5/5] common/encrypt: verify the key identifiers 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=20220313010559.545995-5-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=fstests@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: 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).