lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20191219183854.GA54076@gmail.com>
Date:   Thu, 19 Dec 2019 10:38:55 -0800
From:   Eric Biggers <ebiggers@...nel.org>
To:     Michal Suchanek <msuchanek@...e.de>
Cc:     linux-crypto@...r.kernel.org,
        Herbert Xu <herbert@...dor.apana.org.au>,
        "David S. Miller" <davem@...emloft.net>,
        Maxime Coquelin <mcoquelin.stm32@...il.com>,
        Alexandre Torgue <alexandre.torgue@...com>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] crypto: testmgr: allow building a copy as loadable
 module for testing.

On Thu, Dec 19, 2019 at 05:06:36PM +0100, Michal Suchanek wrote:
> There is no way to just run the tests built into testmgr. Also it is
> rarely possible to build testmgr modular due to KConfig dependencies.
> 
> Add a module that does not provide infrastructure, just runs testmgr
> tests.
> 
> Signed-off-by: Michal Suchanek <msuchanek@...e.de>

Why does this need to be a kernel module?  Since the self-tests are already run
at algorithm registration time, it's already possible to use AF_ALG or
crypto_user to allocate all algorithms which have self-tests.

- Eric

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ