From: "chunhui.jia" <chunhui.jia@linux.intel.com>
To: "Kun Zhao" <zkxz@hotmail.com>,
"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: overlayFS security concern
Date: Sat, 20 Feb 2021 08:52:58 +0800 [thread overview]
Message-ID: <60305D66.2050303@linux.intel.com> (raw)
In-Reply-To: <BYAPR14MB23420BA1183F22A48EF8B97ACF839@BYAPR14MB2342.namprd14.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 962 bytes --]
Maintaining 2 different build configurations would be possible solution: dev build and release build.
1. enable debugging tech in dev build.
2. when using openbmc for product, disable all potential ways that could harm security.
2021-02-20
chunhui.jia
发件人：Kun Zhao <zkxz@hotmail.com>
发送时间：2021-02-20 08:31
主题：overlayFS security concern
收件人："openbmc@lists.ozlabs.org"<openbmc@lists.ozlabs.org>
抄送：
Hi Team,
Have the following case ever been discussed before?,
Anyone knows the root password will be able to let bmc run their own code by scp the code into bmc with the same file path as any services in rootfs. It will make the secure boot totally useless.
So besides,
1. disable scp (but scp is one of the firmware upload way)
2. don’t use overlayFS (but it’s really useful for debugging during develop, and configuration management)
Any other solutions?
Thanks.
Kun
[-- Attachment #2: Type: text/html, Size: 6467 bytes --]
next prev parent reply other threads:[~2021-02-20 0:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-20 0:31 overlayFS security concern Kun Zhao
2021-02-20 0:52 ` chunhui.jia [this message]
2021-02-20 1:13 ` Kun Zhao
2021-02-20 1:17 ` chunhui.jia
2021-02-20 1:16 ` Andrew Jeffery
2021-02-20 16:50 ` Patrick Williams
2021-02-20 22:29 ` Michael Richardson
2021-02-23 5:22 ` Lei Yu
2021-02-23 5:49 ` Milton Miller II
2021-02-22 17:36 ` overlayFS security concern - threat model Joseph Reynolds
2021-03-03 17:55 ` Kun Zhao
2021-03-03 18:00 ` Joseph Reynolds
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=60305D66.2050303@linux.intel.com \
--to=chunhui.jia@linux.intel.com \
--cc=openbmc@lists.ozlabs.org \
--cc=zkxz@hotmail.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.