From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Proposed patch: allow setting an hashed root password
Date: Sun, 22 Mar 2015 17:14:54 +0100 [thread overview]
Message-ID: <550EEA7E.8000207@mind.be> (raw)
In-Reply-To: <20150322160022.GC4724@free.fr>
On 22/03/15 17:00, Yann E. MORIN wrote:
> Lorenzo, All,
>
> On 2015-03-22 16:09 +0100, Lorenzo Catucci spake thusly:
>> Please find enclosed my proposed patch. I've posted the patch to a GH fork of
>> the main repository too: look at the ?hashed_root_pw? branch of
>>
>> https://github.com/lmctv/buildroot
>>
>> The reason I've enabled the new ?BR2_TARGET_GENERIC_ROOT_PASSWD_HASH?
>> configuration option is being able to set a "*" password hash for the root
>> user without being forced to put a static /etc/shadow inside BR2_ROOTFS_OVERLAY.
>>
>> Even if setting a "real" password, I think the option to put a sha256 or
>> sha512 hash in the .config is a lot less scary than putting a plaintext
>> password, especially in the case of sha512 .
>>
>> Thank you very much, yours
>>
>> lorenzo m catucci
>>
>
> NAK.
What Yann wants to say is:
Thank you, Lorenzo, for your patch. However, you have not followed the patch
submission guidelines. Patches should be submitted in-line, preferably using git
send-email. Any "personal" comments can be added below a --- line after your
Signed-off-by.
>
> First, the commit log should only explain the technical reasons for the
> change, and not contain "personal" messages:
>
> first line, short explanation
>
> One (or more) paragraph explainging the current situation and why
> you believe it is incorrect.
>
> One (or more) paragraph explaining what you changed.
>
> Signed-ogg-by: Your Real Name <your-email@somehwere.net>
>
> Second, there's something odd: clearly the patch prefers the hashed
> password over the clear-text one, but does not prevent the user to set
> both.
Therefore, perhaps a better approach is to detect the $-pattern of an
already-encrypted password in package/mkpasswd/mkpasswd.c and skip the hashing
in that case.
>
> Third, if you want to do tricky password handling like this, I think it
> would be better if you passed a "user table" (BR2_ROOTFS_USERS_TABLES)
> that defines the root user and its password, like documented in the
> mkuser infra:
> http://buildroot.net/downloads/manual/manual.html#makeuser-syntax
+1 to that.
So perhaps a better idea is to add that to the help text of
BR2_TARGET_GENERIC_ROOT_PASSWD.
Regards,
Arnout
>
> Regards,
> Yann E. MORIN.
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
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:[~2015-03-22 16:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-22 15:09 [Buildroot] Proposed patch: allow setting an hashed root password Lorenzo Catucci
2015-03-22 16:00 ` Yann E. MORIN
2015-03-22 16:14 ` Arnout Vandecappelle [this message]
2015-03-22 17:31 ` Yann E. MORIN
[not found] ` <550F3EDE.8090106@ccd.uniroma2.it>
2015-03-22 22:56 ` Yann E. MORIN
2015-03-23 11:05 ` Johan Oudinet
2015-03-23 18:48 ` Yann E. MORIN
2015-03-23 23:30 ` [Buildroot] [PATCH v2] Restructure root password handling Lorenzo M. Catucci
2015-03-24 12:13 ` [Buildroot] [PATCH v3] " Lorenzo M. Catucci
2015-03-24 18:56 ` Yann E. MORIN
2015-03-24 0:03 ` [Buildroot] Proposed patch: allow setting an hashed root password Lorenzo M. Catucci
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=550EEA7E.8000207@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