openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Joseph Reynolds <jrey@linux.ibm.com>
To: "Thomaiyar,
	Richard Marian" <richard.marian.thomaiyar@linux.intel.com>,
	openbmc <openbmc@lists.ozlabs.org>,
	Vernon Mauery <vernon.mauery@linux.intel.com>,
	Deepak Kodihalli <deepak.kodihalli.83@gmail.com>,
	Ratan Gupta <ratankgupta31@gmail.com>,
	Tom Joseph <rushtotom@gmail.com>
Subject: Is priv-noaccess needed?
Date: Wed, 16 Feb 2022 14:32:05 -0600	[thread overview]
Message-ID: <41f57009-93da-2920-8074-40f8d146519d@linux.ibm.com> (raw)
In-Reply-To: <cb1a8c54-5a5e-cc07-2f41-95c2036b4dc9@linux.ibm.com>

User manager and IPMI maintainers (and please forward to additional 
interested parties):

We are trying to understand how the NoAccess (priv-noaccess) role is 
used in OpenBMC.  See the discussion below, the gerrit review, and the 
IPMI questions.

What are the use cases?  What is this role used for?  If we need this 
role, let's understand why.  Otherwise, can we deprecate this role and 
remove it?

Joseph


-------- Forwarded Message --------
Subject: 	Re: Security Working Group meeting - Wednesday February 16 - 
results
Date: 	Wed, 16 Feb 2022 13:31:25 -0600
From: 	Joseph Reynolds <jrey@linux.ibm.com>
To: 	openbmc <openbmc@lists.ozlabs.org>



On 2/16/22 7:21 AM, Joseph Reynolds wrote:
> This is a reminder of the OpenBMC Security Working Group meeting 
> scheduled for this Wednesday February 16 at 10:00am PDT.
>
> We'll discuss the following items on the agenda 
> <https://docs.google.com/document/d/1b7x9BaxsfcukQDqbvZsU2ehMq4xoJRQvLxxsDUWmAOI>, 
> and anything else that comes up:

Attended: Joseph, Daniil, Dhananjay, Dick, James, Jiang


> 1.Do we need to discuss the concept and need for NoAccess users and 
> how they would be different from disabled BMC user accounts?  See 
> discussion in 
> https://gerrit.openbmc-project.xyz/c/openbmc/bmcweb/+/49295 
> <https://gerrit.openbmc-project.xyz/c/openbmc/bmcweb/+/49295>

DISCUSSION:

Does the project have any NoAccess (priv-noaccess) users?

Is noaccess needed to implement IPMI Callback users?

Note that we prefer to disable ipmi users, not change their role.

Can ipmitool be used to create a callback user?  If so, what role does 
phosphor-user-manager use for that user?

Is the IPMI callback role deprecated?  Can we remove it from OpenBMC?

Is callback needed to implement trusted system interfaces and 
sessionless interfaces IPMB?

...snip...

Joseph

>
> Access, agenda and notes are in the wiki:
> https://github.com/openbmc/openbmc/wiki/Security-working-group 
> <https://github.com/openbmc/openbmc/wiki/Security-working-group>
>
> - Joseph


      reply	other threads:[~2022-02-16 20:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-16 13:21 Security Working Group meeting - Wednesday February 16 Joseph Reynolds
2022-02-16 19:31 ` Security Working Group meeting - Wednesday February 16 - results Joseph Reynolds
2022-02-16 20:32   ` Joseph Reynolds [this message]

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=41f57009-93da-2920-8074-40f8d146519d@linux.ibm.com \
    --to=jrey@linux.ibm.com \
    --cc=deepak.kodihalli.83@gmail.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=ratankgupta31@gmail.com \
    --cc=richard.marian.thomaiyar@linux.intel.com \
    --cc=rushtotom@gmail.com \
    --cc=vernon.mauery@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).