public inbox for linux-integrity@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Berger <stefanb@linux.ibm.com>
To: linux-integrity@vger.kernel.org
Cc: zohar@linux.ibm.com, Stefan Berger <stefanb@linux.ibm.com>
Subject: [ima-evm-utils PATCH] Add note for how password needs to be provided when -p is used
Date: Tue, 21 Nov 2023 13:18:11 -0500	[thread overview]
Message-ID: <20231121181811.43560-1-stefanb@linux.ibm.com> (raw)

Add a note describing how a password needs to be provided when -p
is used.

Signed-off-by: Stefan Berger <stefanb@linux.ibm.com>
---
 README       | 2 +-
 src/evmctl.c | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/README b/README
index 7239dda..54746ef 100644
--- a/README
+++ b/README
@@ -59,7 +59,7 @@ OPTIONS
       --keyid-from-cert file
                      read keyid value from SKID of a x509 cert file
   -o, --portable     generate portable EVM signatures
-  -p, --pass         password for encrypted signing key
+  -p, --pass         password for encrypted signing key; use -p<password>
   -r, --recursive    recurse into directories (sign)
   -t, --type         file types to fix 'fxm' (f: file)
                      x - skip fixing if both ima and evm xattrs exist (use with caution)
diff --git a/src/evmctl.c b/src/evmctl.c
index 8caf9bd..2710a27 100644
--- a/src/evmctl.c
+++ b/src/evmctl.c
@@ -2851,7 +2851,7 @@ static void usage(void)
 		"      --keyid-from-cert file\n"
 		"                     read keyid value from SKID of a x509 cert file\n"
 		"  -o, --portable     generate portable EVM signatures\n"
-		"  -p, --pass         password for encrypted signing key\n"
+		"  -p, --pass         password for encrypted signing; use -p<password>\n"
 		"  -r, --recursive    recurse into directories (sign)\n"
 		"  -t, --type         file types to fix 'fxm' (f: file)\n"
 		"                     x - skip fixing if both ima and evm xattrs exist (use with caution)\n"
-- 
2.42.0


                 reply	other threads:[~2023-11-21 18:18 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20231121181811.43560-1-stefanb@linux.ibm.com \
    --to=stefanb@linux.ibm.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=zohar@linux.ibm.com \
    /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