From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv5] system: allow/disallow root login, accept encoded passwords
Date: Tue, 14 Apr 2015 21:17:58 +0200 [thread overview]
Message-ID: <552D67E6.5050300@mind.be> (raw)
In-Reply-To: <20150414175443.GA4053@free.fr>
On 14/04/15 19:54, Yann E. MORIN wrote:
[snip]
>> However, since the default is y while it is normally n, and since we have to do
>> something special for the n case, wouldn't it make more sense to call it
>> BR2_TARGET_DISABLE_ROOT_LOGIN?
>
> Well, I do really prefer positive naming; and we tend to use such
> positive logic about everywhere...
>
> That the internals are "more complex" (and that still has to be proven)
> is irrelevant to what we present to the user. At the extreme, we could
> always have a hidden variable that just negates the visible one.
OK for me. A hidden variable would be overkill.
[snip]
>>> +SYSTEM_ROOT_PASSWORD = $(TARGET_GENERIC_ROOT_PASSWD)
>>> +else
>>> +SYSTEM_ROOT_PASSWORD = $(shell $(MKPASSWD) -m "$(TARGET_GENERIC_PASSWD_METHOD)" "$(TARGET_GENERIC_ROOT_PASSWD)")
>>> +endif
>>> +else # !BR2_TARGET_ENABLE_ROOT_LOGIN
>>> +SYSTEM_ROOT_PASSWORD = *
>>
>> Even though Peter prefers positive logic, I think in this case it is more
>> important to keep the logic close to the condition, i.e.:
>>
>> ifeq ($(BR2_TARGET_ENABLE_ROOT_LOGIN),)
>> SYSTEM_ROOT_PASSWORD = *
>> else ifeq ($(TARGET_GENERIC_ROOT_PASSWD),)
>> ...
>
> Well, that was what Thomas initially suggested. But like Peter, I do
> really prefer positive logic, so I'm heavily tempted to keep what I
> wrote, unless others speak up and shout (sooned rather than later!). ;-)
That's two against two then :-)
But since you're the patch owner and Peter is the BDFL, I guess it will be
positive logic.
Regards,
Arnout
>
> Thanks for the review! :-)
>
> Regards,
> Yann E. MORIN.
>
--
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: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
prev parent reply other threads:[~2015-04-14 19:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 21:42 [Buildroot] [PATCHv5] system: allow/disallow root login, accept encoded passwords Yann E. MORIN
2015-04-12 15:19 ` Lorenzo M. Catucci
2015-04-13 22:50 ` Arnout Vandecappelle
2015-04-14 17:54 ` Yann E. MORIN
2015-04-14 19:17 ` Arnout Vandecappelle [this message]
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=552D67E6.5050300@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