Re: [PATCH] keys: allow request-key path to be configured via Kconfig
Jarkko Sakkinen <[email protected]> Mon, 15 Jun 2026 14:49:53 +0300
| Newsgroups | org.kernel.vger.keyrings,org.kernel.vger.linux-kernel,org.kernel.vger.linux-security-module |
|---|---|
| Message-ID | <[email protected]> |
On Wed, Jun 10, 2026 at 02:37:41PM +0100, Gary Guo wrote: > On Wed Jun 10, 2026 at 1:57 PM BST, Jarkko Sakkinen wrote: > > On Mon, Jun 08, 2026 at 11:30:06AM +0100, Gary Guo wrote: > >> > >> This is really just for distros to be able to configure where /sbin is located. > >> Given usr merge and (some distros) bin/sbin merge, the canonical path of > >> request-key binary is very likely not /sbin/request-key anymore, so it seems to > >> make sense to me to allow this to be changed rather than always go through > >> compatibility symlinks. > > > > I doubt there's a huge demand other than NixOS. Just basing this on that > > no other noise have been made so far. > > Just to add on this, both Fedora and openSUSE for example changes their > CONFIG_MODPROBE_PATH to be /usr/sbin/modprobe after /usr merge. They still have > the /sbin -> /usr/sbin symlink available, so it's not like they cannot work with > /sbin/request-key, but I would think that if the option is available then they > might switch to use /usr/sbin/request-key, too. > > After all, why would one perform a symlink walk for no reason? > > Best, > Gary It's not who is right or who is wrong. "The representation of the argument" is not working here. Back to the drawing board... BR, Jarkko