linux-kernel - Re: Use cryptd(%s) as cryptd-ed algorithm name instead of %s

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] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 14 Jan 2009 17:53:59 +1100
From:	Herbert Xu <herbert@...dor.apana.org.au>
To:	Huang Ying <ying.huang@...el.com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-crypto@...r.kernel.org" <linux-crypto@...r.kernel.org>
Subject: Re: Use cryptd(%s) as cryptd-ed algorithm name instead of %s

On Wed, Jan 14, 2009 at 02:44:08PM +0800, Huang Ying wrote:
> Because:
> 
> 1. if use %s, you can only request cryptd(<driver name>), not
>    cryptd(<alg name>), because generated new algorithm instance has
>    algorithm name: <alg name> and driver name cryptd(<driver name>).

This is intentional.  For the purposes we talked about we should
be requesting cryptd(<driver name>), as otherwise you may end up
with someone else's AES algorithm as the base.

> 2. Generated cryptd-ed algorithm will have the same algorithm name and
>    higher priority, but some user may not want to use cryptd-ed
>    version.

The priority shouldn't be an issue in our case since the AES-NI
algorithm should register itself as an ablkcipher with an even
higher priority.

Cheers,
-- 
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/