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  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:	Sun, 2 Sep 2007 09:46:10 +0800
From:	Herbert Xu <>
To:	Satyam Sharma <>
Cc:	Andrew Morton <>,
	KAMEZAWA Hiroyuki <>,
	Linux Kernel Mailing List <>,
	Linux Crypto Mailing List <>
Subject: Re: 2.6.23-rc4-mm1

On Sun, Sep 02, 2007 at 02:39:15AM +0530, Satyam Sharma wrote:
> Tangential, but I've often wondered what are the upsides of keeping
> CONFIG_CRYPTO_ALGAPI as a separate config option in the first place? Every
> single item in crypto/ ends up "select"ing it (directly or transitively)
> so it makes all sense to just do away with it and keep it == CONFIG_CRYPTO
> in the Makefile, thusly:

NACK.  ALGAPI exists so that it can be built as a module, as
opposed to CRYPTO which is always built-in.  It's already
invisible to the user so I don't see why you have a problem
with it.

Visit Openswan at
Email: Herbert Xu ~{PmV>HI~} <>
Home Page:
PGP Key:
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists