Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Danomi Manchego <danomimanchego123@gmail.com>
Cc: "Stefan Sørensen" <stefan.sorensen@spectralink.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] libpwquality: fix PAM module path
Date: Fri, 26 Jul 2024 08:43:11 +0200	[thread overview]
Message-ID: <20240726084311.227da789@windsurf> (raw)
In-Reply-To: <20240726025539.30665-1-danomimanchego123@gmail.com>

On Thu, 25 Jul 2024 22:55:39 -0400
Danomi Manchego <danomimanchego123@gmail.com> wrote:

> The libpwquality package provides the pam_pwquality PAM module - the
> replacement for pam_cracklib that was dropped from linux-pam back in
> version 1.5.0.  However, it currently installs it to the wrong place,
> so passwd and friends fail to find it.  This commit sets the security
> directory path to /lib/security to match the corresponding setting in
> linux-pam.mk.
> 
> Signed-off-by: Danomi Manchego <danomimanchego123@gmail.com>
> ---
>  package/libpwquality/libpwquality.mk | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Thanks for the fix! Could you indicate more clearly in the commit log
which Buildroot commit caused the regression? Is it the bump of
linux-pam to >= 1.5.0 which happened in
276f1e0a896698abec85500a86686bf72c79eb91 ? At the time, was
libpwquality already providing a replacement PAM module ? If not, when
did libpwquality introduced this PAM module ?

Indeed, libpwquality had this optional dependency on linux-pam since
the package was added in 462040443ca943694fc59ec8380c82f8bf9aaddc, back
in 2017.

The whole reason why I'm asking for this additional detail is to
understand whether or not this patch needs to be backported to our LTS
branch, and therefore instead of just "fixing a problem" we need to
understand since when the problem started to exist.

Thanks a lot!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2024-07-26  6:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-26  2:55 [Buildroot] [PATCH 1/1] libpwquality: fix PAM module path Danomi Manchego
2024-07-26  6:43 ` Thomas Petazzoni via buildroot [this message]

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=20240726084311.227da789@windsurf \
    --to=buildroot@buildroot.org \
    --cc=danomimanchego123@gmail.com \
    --cc=stefan.sorensen@spectralink.com \
    --cc=thomas.petazzoni@bootlin.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