From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 6938] New: mkuser script generates wrong password for new user in target/etc/shadow
Date: Thu, 27 Feb 2014 10:49:38 +0000 (UTC) [thread overview]
Message-ID: <bug-6938-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=6938
Summary: mkuser script generates wrong password for new user in
target/etc/shadow
Product: buildroot
Version: 2013.11
Platform: PC
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: poli at centrum.cz
CC: buildroot at uclibc.org
Estimated Hours: 0.0
I've modified my mkusers script from buildroot-2013.11/support/scripts to
generate correct passwords for manually added users from custom packages. I've
renamed files, so the changes are clear.
diff -u mkusers_2013.11 mkusers_2013.11_modified
--- mkusers_2013.11 2014-02-27 11:06:38.000000000 +0100
+++ mkusers_2013.11_modified 2014-02-27 11:05:15.000000000 +0100
@@ -261,7 +261,7 @@
#----------------------------------------------------------------------------
# Encode a password
-encode_password() {
+encode_passwd() {
local passwd="${1}"
mkpasswd -m "${PASSWD_METHOD}" "${passwd}"
@@ -313,7 +313,7 @@
_passwd="$( encode_passwd "${passwd#=}" )"
;;
*)
- _passwd="${passwd}"
+ _passwd="$( encode_passwd "${passwd}" )"
;;
esac
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2014-02-27 10:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 10:49 bugzilla at busybox.net [this message]
2014-02-27 12:17 ` [Buildroot] [Bug 6938] mkuser script generates wrong password for new user in target/etc/shadow bugzilla at busybox.net
2014-02-27 12:32 ` bugzilla at busybox.net
2014-02-27 12:50 ` bugzilla at busybox.net
2014-02-27 13:01 ` bugzilla at busybox.net
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=bug-6938-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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 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.