From: Philip Balister <philip@balister.org>
To: Patrick Ohly <patrick.ohly@intel.com>,
Robert Yang <liezhi.yang@windriver.com>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/2] base-passwd: set root's default password to 'root'
Date: Thu, 24 Nov 2016 09:09:07 -0500 [thread overview]
Message-ID: <d0a381df-850b-6a63-7f7e-47741618cf87@balister.org> (raw)
In-Reply-To: <1479973589.6873.15.camel@intel.com>
On 11/24/2016 02:46 AM, Patrick Ohly wrote:
> On Thu, 2016-11-24 at 11:38 +0800, Robert Yang wrote:
>> Currently, debug-tweaks is in EXTRA_IMAGE_FEATURES by default for poky, and
>> there is no passwd, so that user can login easily without a passwd, I think
>> that current status is more unsafe ?
>
> Both well-known password and no password are unsafe. User "root" with
> password "root" is not even "more" safe already now, because tools that
> brute-force logins try that. Choosing something else would be a bit
> safer for a short while until the tools add it to their dictionary.
>
> Poky is also targeting a different audience than OE-core. Poky can
> assume to be used in a secure environment, OE-core can't (because it
> might be used for all kinds of devices).
>
That is the first time I've heard Poky is targeting an audience assumed
to be running in a secure environment. Should we document what Poky this
somewhere? From where I sit, this seems to be an odd limitation.
Philip
next prev parent reply other threads:[~2016-11-24 14:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 7:49 [PATCH 0/2] fix can't login when debug-tweaks is not in IMAGE_FEATURES Robert Yang
2016-11-23 7:49 ` [PATCH 1/2] rootfs-postcommands.bbclass: fix zap_empty_root_password Robert Yang
2016-11-23 7:49 ` [PATCH 2/2] base-passwd: set root's default password to 'root' Robert Yang
2016-11-23 11:16 ` Patrick Ohly
2016-11-23 14:17 ` Burton, Ross
2016-11-24 2:01 ` Robert Yang
2016-11-24 3:18 ` Paul Eggleton
2016-11-24 3:38 ` Robert Yang
2016-11-24 7:46 ` Patrick Ohly
2016-11-24 8:27 ` Robert Yang
2016-11-24 14:09 ` Philip Balister [this message]
2016-11-24 14:54 ` Patrick Ohly
2016-11-24 18:59 ` Paul Eggleton
2016-11-29 1:57 ` Khem Raj
2016-11-29 2:45 ` Robert Yang
2016-11-29 3:45 ` Paul Eggleton
2016-11-29 5:36 ` Robert Yang
2016-11-29 6:27 ` Paul Eggleton
2016-11-24 7:51 ` Mike Looijmans
2016-11-30 3:15 ` [PATCH 0/2] fix can't login when debug-tweaks is not in IMAGE_FEATURES Robert Yang
2016-11-30 9:28 ` ChenQi
2016-11-30 9:32 ` ChenQi
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=d0a381df-850b-6a63-7f7e-47741618cf87@balister.org \
--to=philip@balister.org \
--cc=liezhi.yang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=patrick.ohly@intel.com \
--cc=paul.eggleton@linux.intel.com \
/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.