From: "Thomaiyar, Richard Marian" <richard.marian.thomaiyar@linux.intel.com>
To: "Tony Lee (李文富)" <Tony.Lee@quantatw.com>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: Question of ipmi command "Set User Access" in phosphor-host-ipmid
Date: Mon, 25 May 2020 21:58:17 +0530 [thread overview]
Message-ID: <e4c12ff6-3387-3dc6-eafa-42e5ac830079@linux.intel.com> (raw)
In-Reply-To: <e46d19fbea37479ca10df26e35d474b2@quantatw.com>
Hi Tony,
Only IPMI offers channel based user level privilege as of now, Redfish
uses single privilege across all channels. OpenBMC user management is
designed to have single user level privilege. IPMI is designed to bind
one of the channel privilege user to the user management, and rest
maintain in it's own database. LAN 1 is used for that sync.
Note: Discussion started in Redfish forum to have a channel based
restriction, but it's not yet materialized and requires more takers.
Regards,
Richard
On 5/25/2020 12:58 PM, Tony Lee (李文富) wrote:
> In the process of creating an user,
> I used the ipmi command "ipmitool priv <user id> <privilege level> [<channel number>]".
> The "UserPrivilege" of the user I created in dbus is empty. Because my LAN channel number is not 1.
>
> https://github.com/openbmc/phosphor-host-ipmid/blob/master/user_channel/user_mgmt.cpp#L878
>
> Why did it need to check the request channel number before setting the dbus?
> I can't find the related restriction of it in "Set User Access Command" in IPMI SPEC.
>
> Thanks
> Best Regards,
> Tony
next prev parent reply other threads:[~2020-05-25 16:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 7:28 Question of ipmi command "Set User Access" in phosphor-host-ipmid Tony Lee (李文富)
2020-05-25 16:28 ` Thomaiyar, Richard Marian [this message]
2020-05-28 8:09 ` Tony Lee (李文富)
2020-05-28 10:21 ` Thomaiyar, Richard Marian
2020-06-01 18:56 ` 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=e4c12ff6-3387-3dc6-eafa-42e5ac830079@linux.intel.com \
--to=richard.marian.thomaiyar@linux.intel.com \
--cc=Tony.Lee@quantatw.com \
--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.