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: [PATCH v4 0/9] ima-evm-utils: Add support for signing with pkcs11 URIs
Date: Mon, 13 Sep 2021 18:18:04 -0400 [thread overview]
Message-ID: <20210913221813.2554880-1-stefanb@linux.ibm.com> (raw)
This series of patches adds support for signing with pkcs11 URIs so that
pkcs11-enabled devices can also be used for file signing.
Extend the existing sign_verify.test with tests for the new pkcs11 URI support.
Use SoftHSM, when available, as a pkcs11 device for testing.
Stefan
v4:
- Addressed Mimi's comments on v3
v3:
- Used commit messages Mimi suggested
- 7/9: Split off imported script into own patch
- 8/9: Added missing EVMCTL_ENGINE variable that allowed to enable Debian
and Ubuntu testing in 9/9; improvements on setup and teardown
functions
- 9/9: Installation of required packages on Debian and Ubuntu
Stefan Berger (9):
evmctl: Implement support for EVMCTL_KEY_PASSWORD environment variable
evmctl: Handle failure to initialize the openssl engine
evmctl: Implement function for setting up an OpenSSL engine
evmctl: Define and use an ENGINE field in libimaevm_params
evmctl: use the pkcs11 engine for pkcs11: prefixed URIs
libimaevm: Add support for pkcs11 private keys for signing a v2 hash
tests: Import softhsm_setup script to enable pkcs11 test case
tests: Extend sign_verify test with pkcs11-specific test
tests: Get the packages for pkcs11 testing on the CI/CD system
README | 5 +
ci/alt.sh | 3 +
ci/debian.sh | 3 +-
ci/fedora.sh | 8 ++
ci/tumbleweed.sh | 3 +
src/evmctl.c | 54 +++++---
src/imaevm.h | 2 +
src/libimaevm.c | 47 +++++--
tests/functions.sh | 45 ++++++-
tests/ima_hash.test | 2 +-
tests/sign_verify.test | 52 ++++++--
tests/softhsm_setup | 293 +++++++++++++++++++++++++++++++++++++++++
12 files changed, 473 insertions(+), 44 deletions(-)
create mode 100755 tests/softhsm_setup
--
2.31.1
next reply other threads:[~2021-09-13 22:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-13 22:18 Stefan Berger [this message]
2021-09-13 22:18 ` [PATCH v4 1/9] evmctl: Implement support for EVMCTL_KEY_PASSWORD environment variable Stefan Berger
2021-09-13 22:18 ` [PATCH v4 2/9] evmctl: Handle failure to initialize the openssl engine Stefan Berger
2021-09-13 22:18 ` [PATCH v4 3/9] evmctl: Implement function for setting up an OpenSSL engine Stefan Berger
2021-09-13 22:18 ` [PATCH v4 4/9] evmctl: Define and use an ENGINE field in libimaevm_params Stefan Berger
2021-09-13 22:18 ` [PATCH v4 5/9] evmctl: use the pkcs11 engine for pkcs11: prefixed URIs Stefan Berger
2021-09-13 22:18 ` [PATCH v4 6/9] libimaevm: Add support for pkcs11 private keys for signing a v2 hash Stefan Berger
2021-09-13 22:18 ` [PATCH v4 7/9] tests: Import softhsm_setup script to enable pkcs11 test case Stefan Berger
2021-09-13 22:18 ` [PATCH v4 8/9] tests: Extend sign_verify test with pkcs11-specific test Stefan Berger
2021-09-13 22:18 ` [PATCH v4 9/9] tests: Get the packages for pkcs11 testing on the CI/CD system Stefan Berger
2021-09-14 15:24 ` [PATCH v4 0/9] ima-evm-utils: Add support for signing with pkcs11 URIs Mimi Zohar
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=20210913221813.2554880-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