From: Mike Snitzer <snitzer@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Cc: Milan Broz <mbroz@redhat.com>
Subject: Re: [PATCH 3/3] dm ioctl: add data secure (bufer wipe) flag
Date: Thu, 3 Feb 2011 10:48:29 -0500 [thread overview]
Message-ID: <20110203154828.GB24255@redhat.com> (raw)
In-Reply-To: <1296691696-23722-3-git-send-email-mbroz@redhat.com>
On Wed, Feb 02 2011 at 7:08pm -0500,
Milan Broz <mbroz@redhat.com> wrote:
> Add DM_SECURE_DATA_FLAG which userspace can use to control
> that all allocated buffers for dm-ioctl are wiped
> immediatelly after use.
>
> The user buffer is wipes as well (we do not want to keep
> and return sensitive data back to userspace if flag is set).
>
> Wiping is useful mainly for cryptsetup to control that key
> is present in memory only on defined places and only
> for time needed.
>
> (For crypt, key can be present in table during load ot table
> status, wait and message command).
>
> Signed-off-by: Milan Broz <mbroz@redhat.com>
> ---
> drivers/md/dm-ioctl.c | 10 ++++++++++
> include/linux/dm-ioctl.h | 12 +++++++++---
> 2 files changed, 19 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/md/dm-ioctl.c b/drivers/md/dm-ioctl.c
> index 189c7ab..9284c38 100644
> --- a/drivers/md/dm-ioctl.c
> +++ b/drivers/md/dm-ioctl.c
> @@ -1518,9 +1518,16 @@ static int copy_params(struct dm_ioctl __user *user, struct dm_ioctl **param)
> if (copy_from_user(dmi, user, tmp.data_size))
> goto fail;
>
> + /* Wipe the user buffer so we do not return it to userspace */
> + if ((tmp.flags & DM_SECURE_DATA_FLAG) &&
> + clear_user(user, tmp.data_size))
> + goto fail;
> +
> *param = dmi;
> return 0;
> fail:
> + if (tmp.flags & DM_SECURE_DATA_FLAG)
> + memset(dmi, 0, tmp.data_size);
> vfree(dmi);
> return -EFAULT;
> }
Maybe save the result of the tmp.flags check in a bool?, e.g.:
const bool wipe_buffers = !!(tmp.flags & DM_SECURE_DATA_FLAG);
Not a big deal if you don't, just an idea.
> @@ -1621,6 +1628,9 @@ static int ctl_ioctl(uint command, struct dm_ioctl __user *user)
> if (!r && copy_to_user(user, param, param->data_size))
> r = -EFAULT;
> out:
> + if (param->flags & DM_SECURE_DATA_FLAG)
> + memset(param, 0, param_size);
> +
> vfree(param);
> return r;
> }
Extra newline at the end not necessary. Those nits aside..
Acked-by: Mike Snitzer <snitzer@redhat.com>
next prev parent reply other threads:[~2011-02-03 15:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-03 0:08 [PATCH 1/3] dm crypt: wipe keys string immediately after key is set Milan Broz
2011-02-03 0:08 ` [PATCH 2/3] dm ioctl: tidy code for next change Milan Broz
2011-02-03 15:39 ` Mike Snitzer
2011-02-03 0:08 ` [PATCH 3/3] dm ioctl: add data secure (bufer wipe) flag Milan Broz
2011-02-03 15:48 ` Mike Snitzer [this message]
2011-02-03 15:52 ` [PATCH 1/3] dm crypt: wipe keys string immediately after key is set Mike Snitzer
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=20110203154828.GB24255@redhat.com \
--to=snitzer@redhat.com \
--cc=dm-devel@redhat.com \
--cc=mbroz@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.