RE: Turning off the D-Bus REST API by default

From: "Garrett, Mike (HPE Server Firmware)" <mike.garrett@hpe.com>
To: Patrick Williams <patrick@stwcx.xyz>, Ali Ahmed <ama213000@gmail.com>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: RE: Turning off the D-Bus REST API by default
Date: Thu, 12 Aug 2021 17:56:59 +0000	[thread overview]
Message-ID: <DF4PR8401MB0634D0AC75CD6A1AC5602C188FF99@DF4PR8401MB0634.NAMPRD84.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <YRU2f8s4T+fBGrE9@heinlein>

Thanks Patrick - I plan to update the HPE machine very soon with several of these fixes.

Mike

> -----Original Message-----
> From: openbmc <openbmc-
> bounces+mike.garrett=hpe.com@lists.ozlabs.org> On Behalf Of Patrick
> Williams
> Sent: Thursday, August 12, 2021 9:56 AM
> To: Ali Ahmed <ama213000@gmail.com>
> Cc: openbmc@lists.ozlabs.org
> Subject: Re: Turning off the D-Bus REST API by default
> 
> On Thu, Aug 12, 2021 at 09:10:01AM -0500, Ali Ahmed wrote:
> > I know there was some previous discussion on this.
> > https://gerrit.openbmc-project.xyz/c/openbmc/bmcweb/+/29344 is
> making
> > the default setting for D-BUS REST API disabled. The D-Bus REST allows
> > authenticated users access to privileged information that may be above
> > their permission level.
> >
> > After this commit to use phosphor-webui or D-Bus REST, you will need
> > to set -Drest=enabled in your bbappend. Note: webui-vue uses Redfish
> > and will not be impacted. Let me know if you have any concerns.
> >
> > -Ali Ahmed
> 
> The following machines/meta-layers seem to still be relying on phosphor-
> webui.
> Is anyone signed up to either switch these to webui-vue or do the
> bbappend?
> 
> ```
> meta-hpe/meta-common/recipes-phosphor/packagegroups/packagegroup-
> hpe-apps.bb:        phosphor-webui \
> meta-hpe/meta-common/recipes-phosphor/packagegroups/packagegroup-
> obmc-apps.bbappend:                           phosphor-webui \
> meta-ibm/meta-palmetto/recipes-phosphor/packagegroups/packagegroup-
> obmc-apps.bbappend:RDEPENDS:${PN}-inventory:append:palmetto = "
> openpower-occ-control phosphor-webui"
> meta-ibm/meta-romulus/recipes-phosphor/packagegroups/packagegroup-
> obmc-apps.bbappend:RDEPENDS:${PN}-extras:append:romulus = "
> phosphor-webui phosphor-image-signing"
> meta-ibm/recipes-phosphor/packagegroups/packagegroup-obmc-
> apps.bbappend:RDEPENDS:${PN}-extras:append:ibm-ac-server = "
> ${POWER_SERVICE_PACKAGES_AC_SERVER} witherspoon-power-supply-
> sync phosphor-webui"
> meta-ibm/recipes-phosphor/packagegroups/packagegroup-obmc-
> apps.bbappend:RDEPENDS:${PN}-extras:append:mihawk = " phosphor-
> webui phosphor-image-signing wistron-ipmi-oem
> ${POWER_SERVICE_PACKAGES_AC_SERVER}"
> meta-ibm/recipes-phosphor/packagegroups/packagegroup-obmc-
> apps.bbappend:RDEPENDS:${PN}-extras:remove:witherspoon-tacoma =
> "obmc-ikvm liberation-fonts uart-render-controller phosphor-webui"
> meta-inspur/meta-on5263m5/recipes-inspur/packagegroups/packagegroup-
> inspur-apps.bb:        phosphor-webui \
> meta-intel-openbmc/meta-common/recipes-
> intel/packagegroups/packagegroup-intel-apps.bb:        phosphor-webui \
> meta-lenovo/meta-common/recipes-lenovo/packagegroups/packagegroup-
> lenovo-apps.bb:        phosphor-webui \
> meta-quanta/meta-olympus-nuvoton/recipes-olympus-
> nuvoton/packagegroups/packagegroup-olympus-nuvoton-apps.bb:
> phosphor-webui \
> meta-supermicro/meta-common/recipes-
> supermicro/packagegroups/packagegroup-supermicro-apps.bb:
> phosphor-webui \
> ```
> 
> Romulus and Palmetto at least are ones we utilize in CI.
> 
> Is whatever hardware testing we do on Witherspoon now moved over to the
> Redfish APIs?  Everything in openbmc-test-automation.
> 
> --
> Patrick Williams