From: Patrick Williams <patrick@stwcx.xyz>
To: OpenBMC List <openbmc@lists.ozlabs.org>
Subject: meta-phosphor: enable `allow-root-login`?
Date: Thu, 30 Dec 2021 07:52:10 -0600 [thread overview]
Message-ID: <Yc25imp2cCDpyXNt@heinlein> (raw)
[-- Attachment #1: Type: text/plain, Size: 1155 bytes --]
Hello,
Looking for opinions, especially from security minded individuals...
In many of our `local.conf.sample` files we enable "debug-tweaks" but for
production builds this is probably not a good idea. I had it turned off on a
production build and ran into a case where we could not log in as root on SSH.
We debugged this down to missing the 'priv-admin' group for root, which is
typically enabled in `phosphor-rootfs-postcommands.bbclass` when either
"debug-tweaks" or "allow-root-login" is enabled.
I am currently enabling this IMAGE_FEATURE in meta-facebook to avoid having this
happen again. Is there any reason why we wouldn't want to enable it by default
in meta-phosphor? There isn't really full support for non-root users in the
base systems anyhow, so is there anyone that wouldn't want "allow-root-login"
enabled by default?
I'm fine leaving this in meta-facebook, but I'm trying to prevent someone else
from having the same issue for what seems like a default case presently.
1. https://github.com/openbmc/openbmc/blob/master/meta-phosphor/classes/phosphor-rootfs-postcommands.bbclass#L10
--
Patrick Williams
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2021-12-30 13:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-30 13:52 Patrick Williams [this message]
2022-01-04 15:32 ` meta-phosphor: enable `allow-root-login`? Johnathan Mantey
2022-01-04 18:26 ` Patrick Williams
2022-01-04 19:24 ` Johnathan Mantey
2022-01-04 18:32 ` Ed Tanous
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=Yc25imp2cCDpyXNt@heinlein \
--to=patrick@stwcx.xyz \
--cc=openbmc@lists.ozlabs.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 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.