From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] Restructure root password handling
Date: Tue, 24 Mar 2015 19:56:07 +0100 [thread overview]
Message-ID: <20150324185607.GB4023@free.fr> (raw)
In-Reply-To: <1427199224-16413-1-git-send-email-lorenzo@sancho.ccd.uniroma2.it>
Lorenzo, All,
On 2015-03-24 13:13 +0100, Lorenzo M. Catucci spake thusly:
> Created a top level boolean entry to enable/disable root login
>
> Allow choosing the root password input format only if root login
> is enabled.
I've sent an updated two-patch series that should supersedes that one.
It is much simpler (IMHO), and more in-line with what we would be
ready to accept, I guess.
Thank you for providing this initial work! :-)
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2015-03-24 18:56 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
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 [this message]
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=20150324185607.GB4023@free.fr \
--to=yann.morin.1998@free.fr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.