From: Stefan Berger <stefanb@linux.ibm.com>
To: linux-integrity@vger.kernel.org
Cc: zohar@linux.ibm.com, dmitry.kasatkin@gmail.com,
Stefan Berger <stefanb@linux.ibm.com>
Subject: [PATCH 0/3] ima-evm-utils: Implement function to only create IMA signature
Date: Tue, 20 Apr 2021 14:30:12 -0400 [thread overview]
Message-ID: <20210420183015.861644-1-stefanb@linux.ibm.com> (raw)
This series of patches implements imaevm_create_ima_signature, a function that
only creates an IMA v2 signature but does not write it into an xattr. This API
fullfills a requirement of rpm-ostree where a tool is being built to sign all
files from something similar to a tar byte stream, though where files are written
to temporary files for signing purpose but the signature itself should not be
written into the filesystem's xattr but simply returned via the API.
Stefan
Stefan Berger (3):
libimaevm: Implement imaevm_create_ima_signature
tests: Add program to create IMA signature with new API call
libimaevm: Have sign_hash_v2 call sign_hash_v2_pkey after reading key
file
src/imaevm.h | 2 +
src/libimaevm.c | 191 ++++++++++++++++++++++++++++++-----
tests/Makefile.am | 6 ++
tests/create_ima_signature.c | 111 ++++++++++++++++++++
tests/sign_verify.test | 21 +++-
5 files changed, 304 insertions(+), 27 deletions(-)
create mode 100644 tests/create_ima_signature.c
--
2.30.2
next reply other threads:[~2021-04-20 18:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-20 18:30 Stefan Berger [this message]
2021-04-20 18:30 ` [PATCH 1/3] libimaevm: Implement imaevm_create_ima_signature Stefan Berger
2021-04-27 0:02 ` Colin Walters
2021-04-27 17:47 ` Stefan Berger
2021-04-27 19:13 ` Stefan Berger
2021-04-20 18:30 ` [PATCH 2/3] tests: Add program to create IMA signature with new API call Stefan Berger
2021-04-20 18:30 ` [PATCH 3/3] libimaevm: Have sign_hash_v2 call sign_hash_v2_pkey after reading key file Stefan Berger
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=20210420183015.861644-1-stefanb@linux.ibm.com \
--to=stefanb@linux.ibm.com \
--cc=dmitry.kasatkin@gmail.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;
as well as URLs for NNTP newsgroup(s).