All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Anuj Mittal" <anuj.mittal@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [zeus][PATCH 10/10] libpam: Remove option 'obscure' from common-password
Date: Thu,  2 Jul 2020 08:54:12 +0800	[thread overview]
Message-ID: <f5b90eeed7366432b39c7cd8c6ee8c23e2d4abe8.1593474787.git.anuj.mittal@intel.com> (raw)
In-Reply-To: <cover.1593474787.git.anuj.mittal@intel.com>

From: haiqing <haiqing.bai@windriver.com>

libpam does not support 'obscure' checks to password,
there are the same checks in pam_cracklib module.
And this fix can remove the below error message while
updating password with 'passwd':
pam_unix(passwd:chauthtok):unrecognized option[obscure]

Signed-off-by: Haiqing Bai <Haiqing.Bai@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
(cherry picked from commit ea761dbac90be77797308666fe1586b05e3df824)
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
---
 meta/recipes-extended/pam/libpam/pam.d/common-password | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

diff --git a/meta/recipes-extended/pam/libpam/pam.d/common-password b/meta/recipes-extended/pam/libpam/pam.d/common-password
index 3896057328..52478dae77 100644
--- a/meta/recipes-extended/pam/libpam/pam.d/common-password
+++ b/meta/recipes-extended/pam/libpam/pam.d/common-password
@@ -10,13 +10,10 @@
 # The "sha512" option enables salted SHA512 passwords.  Without this option,
 # the default is Unix crypt.  Prior releases used the option "md5".
 #
-# The "obscure" option replaces the old `OBSCURE_CHECKS_ENAB' option in
-# login.defs.
-#
 # See the pam_unix manpage for other options.
 
 # here are the per-package modules (the "Primary" block)
-password	[success=1 default=ignore]	pam_unix.so obscure sha512
+password	[success=1 default=ignore]	pam_unix.so sha512
 # here's the fallback if no module succeeds
 password	requisite			pam_deny.so
 # prime the stack with a positive return value if there isn't one already;
-- 
2.25.4


  parent reply	other threads:[~2020-07-02  0:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-02  0:54 [zeus][PATCH 00/10] zeus review request Anuj Mittal
2020-07-02  0:54 ` [zeus][PATCH 01/10] nfs-utils: fix CVE-2019-3689 Anuj Mittal
2020-07-02  0:54 ` [zeus][PATCH 02/10] python3: make gdbm optional Anuj Mittal
2020-07-02  0:54 ` [zeus][PATCH 03/10] python3: un-break disabling the readline PACKAGECONFIG Anuj Mittal
2020-07-02  0:54 ` [zeus][PATCH 04/10] libjpeg-turbo: Fix CVE-2020-13790 Anuj Mittal
2020-07-02  0:54 ` [zeus][PATCH 05/10] qemu: fix CVE-2020-10702 & CVE-2020-13765 Anuj Mittal
2020-07-02  0:54 ` [zeus][PATCH 06/10] gnutls: fixed CVE-2020-13777 Anuj Mittal
2020-07-02  0:54 ` [zeus][PATCH 07/10] kernel-fitimage: introduce FIT_SIGN_ALG Anuj Mittal
2020-07-02  0:54 ` [zeus][PATCH 08/10] kernel.bbclass: Fix Module.symvers support Anuj Mittal
2020-07-04 21:13   ` [OE-core] " Adrian Bunk
2020-07-05 14:09     ` Richard Purdie
2020-07-06  0:14     ` Anuj Mittal
2020-07-02  0:54 ` [zeus][PATCH 09/10] relocatable.bbclass: Avoid an exception if an empty pkgconfig dir exist Anuj Mittal
2020-07-15 20:01   ` [OE-core] " Andre McCurdy
2020-07-02  0:54 ` Anuj Mittal [this message]
2020-07-02  1:02 ` ✗ patchtest: failure for zeus review request (rev3) Patchwork

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=f5b90eeed7366432b39c7cd8c6ee8c23e2d4abe8.1593474787.git.anuj.mittal@intel.com \
    --to=anuj.mittal@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.