From: Marek Vasut <marex@denx.de>
To: Dmitry Kasatkin <d.kasatkin@samsung.com>
Cc: Mimi Zohar <zohar@linux.vnet.ibm.com>,
linux-ima-devel@lists.sourceforge.net,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org,
dmitry.kasatkin@gmail.com
Subject: Re: [PATCH v3 1/3] ima: use ahash API for file hash calculation
Date: Wed, 9 Jul 2014 23:00:25 +0200 [thread overview]
Message-ID: <201407092300.25224.marex@denx.de> (raw)
In-Reply-To: <53BBA6B4.7030705@samsung.com>
On Tuesday, July 08, 2014 at 10:07:16 AM, Dmitry Kasatkin wrote:
[...]
> > Right, but my concern is not about unloading the kernel module, but
> > about the IMA module parameters left initialized. The existing code
> > will continue using ahash (software version), even though the kernel
> > module was unloaded, not shash. My question is about the software
> > implementations of ahash vs. shash performance.
> >
> > Mimi
>
> If HW driver will not be available, ahash loads generic driver which is
> using shash.
> Performance of that will be the same as for using shash directly.
Hi Dmitry, I think Mimi is concerned about the crypto accelerator dying mid-
flight.
Imagine a situation where you have a hardware crypto accelerator connected via
USB. You happily use IMA with this setup for days and then someone comes around
and pulls the USB cable out. Will this be able to cope with such situation, for
example by switching to software operations or such in some sane way ?
I presume that's the concern here.
Best regards,
Marek Vasut
next prev parent reply other threads:[~2014-07-09 21:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-04 12:05 [PATCH v3 0/3] ima: use asynchronous hash API for hash calculation Dmitry Kasatkin
2014-07-04 12:05 ` [PATCH v3 1/3] ima: use ahash API for file " Dmitry Kasatkin
2014-07-07 11:56 ` Mimi Zohar
2014-07-07 13:37 ` Dmitry Kasatkin
2014-07-07 15:44 ` Mimi Zohar
2014-07-07 16:11 ` Dmitry Kasatkin
2014-07-07 16:34 ` Mimi Zohar
2014-07-08 8:07 ` Dmitry Kasatkin
2014-07-09 21:00 ` Marek Vasut [this message]
2014-07-09 23:05 ` Dmitry Kasatkin
2014-07-10 8:02 ` Marek Vasut
2014-07-10 11:18 ` Dmitry Kasatkin
2014-07-10 11:31 ` Marek Vasut
2014-07-04 12:05 ` [PATCH v3 2/3] ima: introduce multi-page collect buffers Dmitry Kasatkin
2014-07-04 12:05 ` [PATCH v3 3/3] ima: provide double buffering for hash calculation Dmitry Kasatkin
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=201407092300.25224.marex@denx.de \
--to=marex@denx.de \
--cc=d.kasatkin@samsung.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-ima-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@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;
as well as URLs for NNTP newsgroup(s).