Re: [RFC PATCH] crypto: pcrypt - Disallow nesting of the pcrypt wrapper

[Eric Biggers]

On Mon, Jul 13, 2026 at 12:30:18PM +1000, Herbert Xu wrote:
> This doesn't fix the problem completely since you can nest in other
> ways, e.g., pcrypt(cryptd(pcrypt(...))).  How about handling the name-
> too-long error more gracefully?

Could we just delete pcrypt instead of continuing to try to fix all the
weird problems it has?  A web search for pcrypt just finds CVEs and
advice not to use it, e.g.
https://github.com/libreswan/libreswan/wiki/Internals:-Cryptographic-Acceleration#obsoleted-ipsec-accelerations

What is the rationale for keeping it?  Who cares about it, other than
people looking for vulnerabilities?

- Eric