From: "Matthias Klein" <matthias.klein@optimeas.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Busybox password hashing algorithm
Date: Wed, 05 Mar 2014 20:21:01 +0000 [thread overview]
Message-ID: <eme7a53074-e075-4a7f-aff4-abd7d0bba770@nb-mak> (raw)
In-Reply-To: <em138b9dea-c66d-44b6-b971-9f950eafe6e4@nb-mak>
Hello Marc,
I have found the solution: the default algorithm for passwd can be set
with the config option CONFIG_FEATURE_DEFAULT_PASSWD_ALGO.
I will send a patch tomorrow.
Best regards,
Matthias
------ Originalnachricht ------
Von: "Matthias Klein" <matthias.klein@optimeas.de>
An: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Gesendet: 05.03.2014 20:19:50
Betreff: Re: [ptxdist] Busybox password hashing algorithm
>Hello Marc,
>
>thanks a lot for the tip !
>
>With that option I can login with a SHA hashed password (starts with
>$6$).
>But if I change the password with passwd (from busybox) I get again a
>"weak" hashed password.
>
>I looked for a similar config option for passwd, but can't find one.
>Is there a way to create SHA hashs with passwd from busybox ?
>
>
>Best regards,
>Matthias
>
>
>------ Originalnachricht ------
>Von: "Marc Kleine-Budde" <mkl@pengutronix.de>
>An: ptxdist@pengutronix.de; "Matthias Klein"
><matthias.klein@optimeas.de>
>Gesendet: 05.03.2014 19:55:14
>Betreff: Re: [ptxdist] Busybox password hashing algorithm
>>On 03/05/2014 07:47 PM, Matthias Klein wrote:
>>> Hello,
>>>
>>> our ptxdist 2014.01.0 based product got an external security audit.
>>> They complained that our passwords in the shadow file are hashed
>>>with
>>> the outdated crypt(3) algorithm.
>>> Her advice is to use bcrypt, PBKDF2 or scrpy.
>>>
>>> We are using busybox for passwd etc.
>>>
>>> Is this a busybox limitation? Or can we change the hashing algorithm
>>>in
>>> busybox?
>>> Or do we need to replace busybox' passwd etc. with something better?
>>
>>Have a look at the BUSYBOX_USE_BB_CRYPT and BUSYBOX_USE_BB_CRYPT_SHA
>>option.
>>
>>Marc
>>
>>--
>>Pengutronix e.K. | Marc Kleine-Budde |
>>Industrial Linux Solutions | Phone: +49-231-2826-924 |
>>Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
>>Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
>>
>
>
>-- ptxdist mailing list
>ptxdist@pengutronix.de
>
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2014-03-05 20:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 19:19 Matthias Klein
2014-03-05 20:21 ` Matthias Klein [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-03-05 18:47 Matthias Klein
2014-03-05 18:55 ` Marc Kleine-Budde
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=eme7a53074-e075-4a7f-aff4-abd7d0bba770@nb-mak \
--to=matthias.klein@optimeas.de \
--cc=ptxdist@pengutronix.de \
/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