Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Peter Kjellerstedt" <peter.kjellerstedt@axis.com>
To: Robert Yang <liezhi.yang@windriver.com>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 1/1] rootfs-postcommands.bbclass: Print a warning when login with root is disabled
Date: Fri, 12 Mar 2021 14:13:17 +0000	[thread overview]
Message-ID: <e67217d10fc244b58cb3ef73815cf37f@XBOX03.axis.com> (raw)
In-Reply-To: <975479fc-e8f4-dccd-56c9-3d830cc5dc54@windriver.com>

> -----Original Message-----
> From: Robert Yang <liezhi.yang@windriver.com>
> Sent: den 9 mars 2021 09:32
> To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>; openembedded-
> core@lists.openembedded.org
> Subject: Re: [OE-core] [PATCH 1/1] rootfs-postcommands.bbclass: Print a
> warning when login with root is disabled
> 
> Hi Peter,
> 
> On 3/5/21 6:18 PM, Peter Kjellerstedt wrote:
> >> -----Original Message-----
> >> From: openembedded-core@lists.openembedded.org <openembedded-
> >> core@lists.openembedded.org> On Behalf Of Robert Yang
> >> Sent: den 5 mars 2021 09:49
> >> To: openembedded-core@lists.openembedded.org
> >> Subject: [OE-core] [PATCH 1/1] rootfs-postcommands.bbclass: Print a
> warning when login with root is disabled
> >>
> >> Fixed:
> >> EXTRA_IMAGE_FEATURES_remove = "debug-tweaks"
> >> $ bitbake core-image-minimal
> >>
> >> Then we can't login to the system with root without any messages. Add a
> warning
> >> makes it easy to debug.
> >>
> >> Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
> >> ---
> >>   meta/classes/rootfs-postcommands.bbclass | 6 +++++-
> >>   1 file changed, 5 insertions(+), 1 deletion(-)
> >>
> >> diff --git a/meta/classes/rootfs-postcommands.bbclass
> b/meta/classes/rootfs-postcommands.bbclass
> >> index 1f27a3d07a..e4fe416ac9 100644
> >> --- a/meta/classes/rootfs-postcommands.bbclass
> >> +++ b/meta/classes/rootfs-postcommands.bbclass
> >> @@ -147,7 +147,11 @@ read_only_rootfs_hook () {
> >>   zap_empty_root_password () {
> >>   	if [ -e ${IMAGE_ROOTFS}/etc/shadow ]; then
> >>   		sed -i 's%^root::%root:*:%'
> ${IMAGE_ROOTFS}/etc/shadow
> >> -        fi
> >> +		grep -q '^root:*:' ${IMAGE_ROOTFS}/etc/shadow
> >
> > That will match any /etc/shadow file with "root:" in it. Change it to:
> >
> > 		grep -q '^root:\*:' ${IMAGE_ROOTFS}/etc/shadow
> 
> Thanks, I will update it.
> 
> >
> > And make this optional. We intentionally do not have a root password set
> in our
> 
> I don't quite understand about "optional", when the command is:
> 
> grep -q '^root:\*:' ${IMAGE_ROOTFS}/etc/shadow
> 
> Then empty root password in shadow is:
> root::
> 
> so empty root password won't be matched?

Sorry, I was unclear. We do not have an empty password, we have 
"root:*:..." in /etc/shadow, and we obviously do not want this warning.

> // Robert

//Peter

> > products when they are delivered due to the state law (SB-327) that went
> into
> > effect on January 1, 2020 in California, which prohibits default
> passwords to
> > be used in IoT products.
> >
> >> +		if [ $? -eq 0 ]; then
> >> +			bbwarn "Login with root user is disabled
> since zap_empty_root_password is enabled"
> >> +		fi
> >> +	fi
> >>   	if [ -e ${IMAGE_ROOTFS}/etc/passwd ]; then
> >>   		sed -i 's%^root::%root:*:%'
> ${IMAGE_ROOTFS}/etc/passwd
> >>   	fi
> >> --
> >> 2.17.1
> >
> > //Peter
> >

  reply	other threads:[~2021-03-12 14:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-05  8:49 [PATCH 0/1] rootfs-postcommands.bbclass: Print a warning when login with root is disabled Robert Yang
2021-03-05  8:49 ` [PATCH 1/1] " Robert Yang
2021-03-05 10:18   ` [OE-core] " Peter Kjellerstedt
2021-03-09  8:32     ` Robert Yang
2021-03-12 14:13       ` Peter Kjellerstedt [this message]
2021-03-15  2:31         ` Robert Yang
2021-03-15 11:14           ` Peter Kjellerstedt

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=e67217d10fc244b58cb3ef73815cf37f@XBOX03.axis.com \
    --to=peter.kjellerstedt@axis.com \
    --cc=liezhi.yang@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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