- "Neil Horman" wrote:
> On Thu, Aug 05, 2010 at 10:17:53PM +0200, Miloslav Trmač wrote:
> > Hello,
> > following is a patchset providing an user-space interface to the
> kernel crypto
> > API. It is based on the older, BSD-compatible, implementation, but
> the
> > user-space interface is dif
On Fri, Aug 6, 2010 at 1:06 AM, Olivier Galibert wrote:
>
> Maybe Linus would be happier if the self-tests were limited (by
> default) to the hardware accelerators? Having a software backup and
> the risk of data loss indeed makes things different.
No. I'd be happier if it was an OPTION.
And it
On Fri, Aug 06, 2010 at 04:39:00PM +0800, Herbert Xu
(herb...@gondor.apana.org.au) wrote:
> So you'd rather have a box that doesn't boot rather than one
> that automatically falls back to software crypto allowing you
> to diagnose and report the problem.
What about kernel boot parameter to test h
El Fri, 6 Aug 2010 09:43:28 +0800
Herbert Xu escribió:
> On Thu, Aug 05, 2010 at 11:21:42AM +0200, Alejandro Riveira Fernández wrote:
> >
> > This fixes a typo in file crypto/Kconfig.
>
> Thanks for the patch. As I've just negated this option, the typo
> text no longer exists in the crypto-2.
Olivier Galibert wrote:
>
> Of course in practice without the tests your boot would probably just
> have failed. Badly-decrypted root partitions tend to be noticed as
> such long before trying to write to them. Then you would have bitched
> on the list and the driver would have been fixed or rem
On Fri, Aug 06, 2010 at 12:50:04AM -0400, Kyle Moffett wrote:
> You should also realize that crypto drivers are very much *NOT* in the
> same situation as most other drivers. Without this test, adding a new
> crypto hardware driver to the kernel is a completely unsafe operation,
> because it could
