summaryrefslogtreecommitdiff
path: root/meta-phosphor
diff options
context:
space:
mode:
authorAdriana Kobylak <anoo@us.ibm.com>2018-11-05 18:35:19 +0300
committerBrad Bishop <bradleyb@fuzziesquirrel.com>2018-11-20 07:02:52 +0300
commit3da8d86d73090a2ffbadf31ce5c0e36c7c3c185e (patch)
tree241afaa5febabe2fb81498270e2ddbdef747abfa /meta-phosphor
parentfb69513910a4fabd9c4861dfdbf862c6cb27c8ca (diff)
downloadopenbmc-3da8d86d73090a2ffbadf31ce5c0e36c7c3c185e.tar.xz
synclist: Only sync network configuration and uuid
There's a scenario where the root password can be disabled, which would be synced as part of the synclist via the password/shadow files, and if a chip switch occurs, the BMC would be locked out because not all the app configuration files are synced to for example enable LDAP. To avoid issues, just sync the network configuration information so that if the BMC is setup with a static IP that the user still has easy access to it, the machine id (uuid) which is used by systemd on startup, and hostname. (From meta-phosphor rev: 803306ebc6565a052a7983a6a41566ec7b6fa2b5) Change-Id: Ic4387851434f23803032b920f391e925034dcbae Signed-off-by: Adriana Kobylak <anoo@us.ibm.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Diffstat (limited to 'meta-phosphor')
-rw-r--r--meta-phosphor/recipes-phosphor/flash/phosphor-software-manager/synclist8
1 files changed, 0 insertions, 8 deletions
diff --git a/meta-phosphor/recipes-phosphor/flash/phosphor-software-manager/synclist b/meta-phosphor/recipes-phosphor/flash/phosphor-software-manager/synclist
index 8213ce6a0..3836673c7 100644
--- a/meta-phosphor/recipes-phosphor/flash/phosphor-software-manager/synclist
+++ b/meta-phosphor/recipes-phosphor/flash/phosphor-software-manager/synclist
@@ -1,11 +1,3 @@
-/etc/dropbear/
-/etc/group
-/etc/gshadow
/etc/hostname
/etc/machine-id
-/etc/passwd
-/etc/shadow
-/etc/ssl/
-/etc/ssl/certs/nginx/
-/etc/ssl/private/
/etc/systemd/network/