From: Bruno Meneguele <bmeneg@redhat.com>
To: zohar@linux.ibm.com, Simon.THOBY@viveris.fr, kgold@linux.ibm.com
Cc: linux-integrity@vger.kernel.org, Bruno Meneguele <bmeneg@redhat.com>
Subject: [PATCH v7 ima-evm-utils 0/2] make default hash algorithm dynamic
Date: Fri, 10 Sep 2021 15:46:59 -0300 [thread overview]
Message-ID: <20210910184701.386163-1-bmeneg@redhat.com> (raw)
In order to allow users to set their own security policies, this patch
adds an option in configuration time to set the default hash algorithm to be
used. Considering that any hash algorithm supported by the kernel can be
used, the chosen algo is then checked against the hash_info.h header file.
At the same time, move from SHA1 to SHA256 default hash algorithm, following
the general movement of dropping SHA1 support in the major distros due to
its weaknesses.
Changelog:
v6 - make user input lower case regardless and rebase code
v5 - remove case insensitive grep
v4 - check against hash_info.h kernel header instead of /proc/crypto
v3 - remove wrong comment from m4 script
v2 - add a config time option for setting DEFAULT_HASH_ALGO.
Bruno Meneguele (2):
set default hash algorithm in configuration time
make SHA-256 the default hash algorithm
README | 2 +-
configure.ac | 2 ++
m4/default-hash-algo.m4 | 36 ++++++++++++++++++++++++++++++++++++
src/evmctl.c | 4 ++--
src/imaevm.h | 4 ++++
src/libimaevm.c | 2 +-
6 files changed, 46 insertions(+), 4 deletions(-)
create mode 100644 m4/default-hash-algo.m4
--
2.31.1
next reply other threads:[~2021-09-10 18:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-10 18:46 Bruno Meneguele [this message]
2021-09-10 18:47 ` [PATCH v7 ima-evm-utils 1/2] set default hash algorithm in configuration time Bruno Meneguele
2021-09-14 15:24 ` Mimi Zohar
2021-09-16 20:54 ` Bruno Meneguele
2021-09-10 18:47 ` [PATCH v7 ima-evm-utils 2/2] make SHA-256 the default hash algorithm Bruno Meneguele
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=20210910184701.386163-1-bmeneg@redhat.com \
--to=bmeneg@redhat.com \
--cc=Simon.THOBY@viveris.fr \
--cc=kgold@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;
as well as URLs for NNTP newsgroup(s).