From: "Stefan Fröberg" <stefan.froberg@petroprogram.com>
To: buildroot@busybox.net
Subject: [Buildroot] Questions abou PAM, cracklib and busybox adduser
Date: Mon, 01 Oct 2012 16:56:42 +0300 [thread overview]
Message-ID: <5069A11A.3060004@petroprogram.com> (raw)
Hello all
I was just wondering if it makes sense to compile the new linux-pam
package that is now in buildroot
with cracklib support ?
I mean, doesn't the busybox adduser applet (or more like, passwd applet)
contain somekind of password strength checking
(CONFIG_FEATURE_PASSWD_WEAK_CHECK) option already ?
I wan't the best password strength checking possible so should I use
plain busybox with CONFIG_FEATURE_PASSWD_WEAK_CHECK enabled or
disable that and compile linux-pam with cracklib ?
Best regards:
Stefan
P.S:
Does anybody happen to have a nice patch to busybox deluser applet so
that it would support
the -r, --remove option (remove user home directory after user has been
removed from /etc/passwd and /etc/shadow)
like shadow package userdel command does ?
Im feeling soooo lazy today to start messing with
shadow-4.1.5.1/src/userdel.c and grokking how to add that to deluser
:-)
reply other threads:[~2012-10-01 13:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5069A11A.3060004@petroprogram.com \
--to=stefan.froberg@petroprogram.com \
--cc=buildroot@busybox.net \
/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