netdev - Re: [PATCH 0/4] crypto: CRYPTO_MAX_ALG

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]

Message-Id: <20170406.135832.1914702009261438916.davem@davemloft.net>
Date:   Thu, 06 Apr 2017 13:58:32 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     herbert@...dor.apana.org.au
Cc:     alexander.sverdlin@...ia.com, linux-crypto@...r.kernel.org,
        netdev@...r.kernel.org
Subject: Re: [PATCH 0/4] crypto: CRYPTO_MAX_ALG_NAME is too low

From: Herbert Xu <herbert@...dor.apana.org.au>
Date: Thu, 6 Apr 2017 16:15:09 +0800

> As the final patch depends on all three it would be easiest if
> we pushed the xfrm patch through the crypto tree.  Steffen/David?

No objections from me for this going through the crypto tree.