From: Vitaly Chikunov <vt@altlinux.org>
To: Mimi Zohar <zohar@linux.vnet.ibm.com>,
Dmitry Kasatkin <dmitry.kasatkin@gmail.com>,
linux-integrity@vger.kernel.org
Cc: "Dmitry V. Levin" <ldv@altlinux.org>
Subject: Re: [PATCH ima-evm-utils] Improve memory handling for private keys and passwords
Date: Fri, 13 Aug 2021 00:46:17 +0300 [thread overview]
Message-ID: <20210812214617.og7eclvb53l3hqip@altlinux.org> (raw)
In-Reply-To: <20210812212143.2223183-1-vt@altlinux.org>
Hi,
On Fri, Aug 13, 2021 at 12:21:43AM +0300, Vitaly Chikunov wrote:
> After CRYPTO_secure_malloc_init OpenSSL will store private keys in
> secure heap. This facility is only available since OpenSSL_1_1_0-pre1
> and enabled for 'ima_sign', 'sign', 'sign_hash', and 'hmac'.
> setvbuf(3) _IONBF is used to hopefully avoid private key and password
> being stored inside of stdio buffers.
I should note that usefulness of this method (of avoiding buffering) is
not proven. I don't find other implementations doing it. So, I'm open to
suggestion of removing it.
Thanks,
>
> Unfortunately, secure heap is not used for the passwords (`-p') due to
> absence of its support in the older OpenSSL where ima-evem-utils still
> should work, thus simple cleansing of password memory is used where
> possible to shorten its lifespan.
>
> Signed-off-by: Vitaly Chikunov <vt@altlinux.org>
> ---
> Perhaps, it will conflict with Bruno's patch, we should decide which
> one goes first if this will be accepted.
>
> src/evmctl.c | 83 ++++++++++++++++++++++++++++++++++++++++++++++---
> src/libimaevm.c | 14 ++++++++-
> 2 files changed, 92 insertions(+), 5 deletions(-)
next prev parent reply other threads:[~2021-08-12 21:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-12 21:21 [PATCH ima-evm-utils] Improve memory handling for private keys and passwords Vitaly Chikunov
2021-08-12 21:46 ` Vitaly Chikunov [this message]
2021-08-13 21:31 ` Mimi Zohar
2021-08-18 21:07 ` Mimi Zohar
2021-08-18 21:17 ` Vitaly Chikunov
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=20210812214617.og7eclvb53l3hqip@altlinux.org \
--to=vt@altlinux.org \
--cc=dmitry.kasatkin@gmail.com \
--cc=ldv@altlinux.org \
--cc=linux-integrity@vger.kernel.org \
--cc=zohar@linux.vnet.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