From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] target: add different methods to encode passwords
Date: Fri, 04 Jan 2013 21:31:07 +0100 [thread overview]
Message-ID: <87lic8n110.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <50E73970.8000404@zacarias.com.ar> (Gustavo Zacarias's message of "Fri, 04 Jan 2013 17:20:00 -0300")
>>>>> "Gustavo" == Gustavo Zacarias <gustavo@zacarias.com.ar> writes:
Gustavo> On 12/30/2012 03:08 PM, Yann E. MORIN wrote:
>> Passwords can be encoded in different ways (from the weakest
>> to the strongest): des, md5, sha-256, sha-512
>>
>> Add a choice entry to select the method, defaulting to 'md5'.
>>
>> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Gustavo> Tested-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
Gustavo> However i'd like to see an option where the root password is untouched,
Gustavo> probably as default.
Gustavo> A slippy finger might get a bad surprise when upgrading to a
Gustavo> new buildroot version and sees it's skeleton root password
Gustavo> zapped away to nothing by surprise - an error that might take
Gustavo> some time to get noticed and might even get shipped. Regards.
Hmm, the root passwd stuff should only only be active if the default
rootfs skeleton is used (so no passwd). I see that's not the case today,
will fix.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2013-01-04 20:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-30 18:08 [Buildroot] [pull request v5] Pull request for branch yem-root-passwd Yann E. MORIN
2012-12-30 18:08 ` [Buildroot] [PATCH 1/1] target: add different methods to encode passwords Yann E. MORIN
2013-01-02 23:21 ` Yann E. MORIN
2013-01-04 20:20 ` Gustavo Zacarias
2013-01-04 20:31 ` Peter Korsgaard [this message]
2013-01-05 10: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=87lic8n110.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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