From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] target: add option to set the root password
Date: Sat, 10 Nov 2012 01:30:55 +0100 [thread overview]
Message-ID: <509DA03F.1020501@mind.be> (raw)
In-Reply-To: <1352503739-20083-1-git-send-email-yann.morin.1998@free.fr>
On 11/10/12 00:28, Yann E. MORIN wrote:
> Add an option in the menuconfig to specify a root password.
>
> If set to empty, no root password is created; otherwise, the password is
> encrypted using MD5 (MD5 is not the default for crypt(3), DES-56 is, but
> MD5 is widely available, not-so-strong, but not-so-weak either).
>
> Add a check for 'mkpasswd' as a new dependency.
Is it necessary to put the plaintext password in the .config? Why not put the
output of mkpasswd in the config, and explain in the help text how to produce
it? Perhaps even with vVj0miIkzZnhg as an example of password root. So the
help text could be:
Set the root password. This is the crypt'ed password as it should
appear in /etc/shadow. To create a password, use the mkpasswd
utility: "mkpasswd -m md5" to create an md5-crypted password.
Note that sha256 or sha512-crypted passwords are preferred, because
md5 is somewhat compromised. However, the default busybox
configuration does not have support for sha256 and sha512 passwords.
Obviously, this will make the patch much simpler, as there won't be a need
anymore to distinguish between no-root-passwd and root-passwd.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2012-11-10 0:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-09 23:28 [Buildroot] [PATCH] target: add option to set the root password Yann E. MORIN
2012-11-10 0:30 ` Arnout Vandecappelle [this message]
2012-11-10 11:48 ` Yann E. MORIN
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=509DA03F.1020501@mind.be \
--to=arnout@mind.be \
--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