From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] busybox: use md5 as default password algorithm
Date: Fri, 11 Mar 2016 01:10:14 +0100 [thread overview]
Message-ID: <56E20CE6.9090500@mind.be> (raw)
In-Reply-To: <87pov2j8mt.fsf@dell.be.48ers.dk>
On 03/10/16 23:00, Peter Korsgaard wrote:
>>>>>> "Gustavo" == Gustavo Zacarias <gustavo@zacarias.com.ar> writes:
>
> > On 10/03/16 17:01, Peter Korsgaard wrote:
> >> So this is what is used when you change password through the busybox
> >> passwd applet or create a new user, right?
> >>
> >> Shouldn't we instead tweak this based on BR2_TARGET_GENERIC_PASSWD_*?
>
> > Yes.
> > This is the lowest-common which is guaranteed to work on all
> > scenarios, once we decide/switch to sha256 as default we can update it
> > here, but i wouldn't defer this until then.
>
> Ehh, yes - But if you have enabled E.G BR2_TARGET_GENERIC_PASSWD_SHA512
> then that is what the busybox passwd applet should use. Having it do md5
> instead of des is still wrong.
Peter, you yourself said that we should limit the amount of KCONFIG_* fixups
we do. And there is no other way to make it depend on the
BR2_TARGET_GENERIC_PASSWD_* choice.
Regards,
Arnout
--
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: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2016-03-11 0:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 19:43 [Buildroot] [PATCH] busybox: use md5 as default password algorithm Gustavo Zacarias
2016-03-10 20:01 ` Peter Korsgaard
2016-03-10 20:03 ` Gustavo Zacarias
2016-03-10 22:00 ` Peter Korsgaard
2016-03-11 0:10 ` Arnout Vandecappelle [this message]
2016-03-22 23:03 ` Thomas Petazzoni
2016-03-24 20:54 ` Peter Korsgaard
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=56E20CE6.9090500@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