On Sat, Sep 14, Dmitry V. Levin wrote:
On Sat, Sep 14, 2019 at 07:17:15AM +0200, Thorsten Kukuk wrote:
> On Fri, Sep 13, Dmitry V. Levin wrote:
>
> > I'm not sure I understand the intent here.
> > Does it make sense to enable econf (by default) when vendordir is not enabled?
> > Does it make sens to enable vendordir when econf is not available?
> > It seems to me that these two have to be either both enabled or both
> > disabled, please correct me if I got it wrong.
>
> It makes sense to enable vendordir even if you don't have econf.
> econf is only used to read login.defs, but for an alternate pam.d
> directory or securetty file, it's not used.
OK, does it make sense to enable econf by default if vendordir is not
enabled?
Yes. As several packages read /etc/login.defs and some of them add their
own variables, this packages could have now their own config snipets
in /etc/login.defs.d/ without the need to patch the shadow sources.
I have updated the pull request, as the patch is meanwhile too big for
the list I haven't attached it.
Thorsten
--
Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS
SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
Managing Director: Felix Imendoerffer (HRB 247165, AG München)