Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] busybox: use md5 as default password algorithm
Date: Thu, 10 Mar 2016 21:01:26 +0100	[thread overview]
Message-ID: <871t7im7ah.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1457638990-27544-1-git-send-email-gustavo@zacarias.com.ar> (Gustavo Zacarias's message of "Thu, 10 Mar 2016 16:43:10 -0300")

>>>>> "Gustavo" == Gustavo Zacarias <gustavo@zacarias.com.ar> writes:

 > DES is terribly outdated and a security vulnerability.
 > Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
 > ---
 >  package/busybox/busybox.config | 2 +-
 >  1 file changed, 1 insertion(+), 1 deletion(-)

 > diff --git a/package/busybox/busybox.config b/package/busybox/busybox.config
 > index 2cf989d..693b9d2 100644
 > --- a/package/busybox/busybox.config
 > +++ b/package/busybox/busybox.config
 > @@ -496,7 +496,7 @@ CONFIG_PASSWD=y
 >  CONFIG_FEATURE_PASSWD_WEAK_CHECK=y
 >  # CONFIG_CRYPTPW is not set
 >  # CONFIG_CHPASSWD is not set
 > -CONFIG_FEATURE_DEFAULT_PASSWD_ALGO="des"
 > +CONFIG_FEATURE_DEFAULT_PASSWD_ALGO="md5"

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_*?

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2016-03-10 20:01 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 [this message]
2016-03-10 20:03   ` Gustavo Zacarias
2016-03-10 22:00     ` Peter Korsgaard
2016-03-11  0:10       ` Arnout Vandecappelle
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=871t7im7ah.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --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