From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1 v2] scripts/mkusers: allow users with no password value set
Date: Tue, 9 Jun 2015 23:13:44 +0200 [thread overview]
Message-ID: <20150609231344.69fed325@free-electrons.com> (raw)
In-Reply-To: <1432403497-4132-1-git-send-email-james.knight@rockwellcollins.com>
Dear James Knight,
On Sat, 23 May 2015 13:51:37 -0400, James Knight wrote:
> The following allows a user definition to specify that a created user
> entry should not have a password value set. Original implementation
> allowed a user definition to provide a password value of "=" (no quotes)
> to generate a crypt-encoded empty string value. In some cases, it may be
> desired to have no value specified for a user's password. By using a
> value "-" for a password, no value will be set in the shadow value.
>
> An example when this can be used is when logging into a terminal.
> Logging into a session with an encoded empty password will prompt a user
> to enter a password since it does not know the password is empty. If the
> password field blank, a login session will not prompt for a password.
>
> Signed-off-by: James Knight <james.knight@rockwellcollins.com>
> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> ---
> Changes v1 -> v2:
> - Correct error in commit message.
> - More explicit example in commit message (suggested by Yann).
>
> docs/manual/makeusers-syntax.txt | 3 ++-
> support/scripts/mkusers | 3 +++
> 2 files changed, 5 insertions(+), 1 deletion(-)
Applied, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-06-09 21:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-23 17:51 [Buildroot] [PATCH 1/1 v2] scripts/mkusers: allow users with no password value set James Knight
2015-06-09 21:13 ` Thomas Petazzoni [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=20150609231344.69fed325@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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