From: "Arnd Bergmann" <arnd@arndb.de>
To: "Geert Uytterhoeven" <geert@linux-m68k.org>,
"Arnd Bergmann" <arnd@kernel.org>
Cc: "'bbrezillon@kernel.org'" <bbrezillon@kernel.org>,
"Arnaud Ebalard" <arno@natisbad.org>,
"Srujana Challa" <schalla@marvell.com>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
"David S . Miller" <davem@davemloft.net>,
"David Howells" <dhowells@redhat.com>,
"Jarkko Sakkinen" <jarkko@kernel.org>,
"Paul Moore" <paul@paul-moore.com>,
"James Morris" <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
"Justin M. Forbes" <jforbes@fedoraproject.org>,
"Jason A . Donenfeld" <Jason@zx2c4.com>,
"Rosen Penev" <rosenp@gmail.com>,
"Ard Biesheuvel" <ardb@kernel.org>,
"James E . J . Bottomley" <James.Bottomley@hansenpartnership.com>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
keyrings@vger.kernel.org, linux-security-module@vger.kernel.org
Subject: Re: [PATCH] [v2] crypto: lib/Kconfig: hide library options
Date: Sun, 30 Mar 2025 10:45:19 +0200 [thread overview]
Message-ID: <4a1e3e4d-a568-4f5f-a6cc-502b9642d0eb@app.fastmail.com> (raw)
In-Reply-To: <CAMuHMdViGZRQL7toi7Arvm5L=OTK1mGmODbckE+427bx4KyWdw@mail.gmail.com>
On Sun, Mar 30, 2025, at 10:34, Geert Uytterhoeven wrote:
> On Fri, 14 Mar 2025 at 17:05, Arnd Bergmann <arnd@kernel.org> wrote:
>
>> --- a/security/keys/Kconfig
>> +++ b/security/keys/Kconfig
>> @@ -60,7 +60,7 @@ config BIG_KEYS
>> bool "Large payload keys"
>> depends on KEYS
>> depends on TMPFS
>> - depends on CRYPTO_LIB_CHACHA20POLY1305 = y
>> + select CRYPTO_LIB_CHACHA20POLY1305
>> help
>> This option provides support for holding large keys within the kernel
>> (for example Kerberos ticket caches). The data may be stored out to
>
> Due to dropping the dependency, this appeared on my radar.
> Should this be selected by one or some of the Kerberos Kconfig symbols?
>
I don't see why: before commit 521fd61c84a1 ("security/keys: rewrite
big_key crypto to use library interface") it was user selectable
without the crypto dependency, and now it got back to that. I think
from the point of view of Kconfig that is how we want it.
Arnd
next prev parent reply other threads:[~2025-03-30 8:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-14 16:05 Arnd Bergmann
2025-03-17 8:36 ` David Howells
2025-03-17 8:37 ` Herbert Xu
2025-03-17 9:04 ` Arnd Bergmann
2025-03-17 12:38 ` Jarkko Sakkinen
2025-03-21 11:06 ` Herbert Xu
2025-03-30 8:34 ` Geert Uytterhoeven
2025-03-30 8:45 ` Arnd Bergmann [this message]
2025-03-30 8:54 ` Geert Uytterhoeven
2025-03-30 9:07 ` Herbert Xu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4a1e3e4d-a568-4f5f-a6cc-502b9642d0eb@app.fastmail.com \
--to=arnd@arndb.de \
--cc=James.Bottomley@hansenpartnership.com \
--cc=Jason@zx2c4.com \
--cc=ardb@kernel.org \
--cc=arnd@kernel.org \
--cc=arno@natisbad.org \
--cc=bbrezillon@kernel.org \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=geert@linux-m68k.org \
--cc=herbert@gondor.apana.org.au \
--cc=jarkko@kernel.org \
--cc=jforbes@fedoraproject.org \
--cc=jmorris@namei.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=rosenp@gmail.com \
--cc=schalla@marvell.com \
--cc=serge@hallyn.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®