summaryrefslogtreecommitdiff
path: root/meta-phosphor/recipes-phosphor/ipmi/phosphor-ipmi-config
AgeCommit message (Collapse)AuthorFilesLines
2020-04-14Add default cs_privilege_levels.json config filejayaprakash Mutyala1-0/+1
As part of below patch, adding default Cipher Suite Privilege Levels config file i.e. cs_privilege_levels.json to /usr/share/ipmi-providers/ https://gerrit.openbmc-project.xyz/#/c/openbmc/phosphor-host-ipmid/ +/21500/ IPMI Spec 13.17 provides a way to pick a "highest level matching proposed algorithms" during RMCPP Open Session Request, and effective privilege levels are decided taking Cipher Suite Privilege Levels into account. This patch initializes Cipher Suite Privilege Levels configurations into a JSON file. By default, admin privileges are given to all Cipher Suites across all channels. (From meta-phosphor rev: 21aff89f885f061a75b26bc09164fdc44a1a749f) Signed-off-by: jayaprakash Mutyala <mutyalax.jayaprakash@intel.com> Change-Id: I66ca032b0c040e8f6055b83044320f85b6fb2ef1 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2020-04-03Remove Cipher suite 3 from cipher listSuryakanth Sekar1-6/+0
Reason: For security reason- HMAC-SHA1 is deprecated. Plesae note: Use latest ipmitool or ipmitool v1.8.18.177.g7ccea28 later Tested: ipmitool lan print <channel> Should not list cipher 3 as supported. (From meta-phosphor rev: 72dbf6344b9abeae6bdc3c721359eef9ec5f67bd) Signed-off-by: Suryakanth Sekar <suryakanth.sekar@linux.intel.com> Change-Id: Idfb3d0f014e3b1e1155be98fac4df741dc97115e Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2019-10-03meta-phosphor: ipmi-config: add default entity mapPatrick Venture1-0/+15
Add an empty entity map json file. The file is expected to be an array, if it is present at all. The file provided by default has no real meaning to your system, therefore you are expected if you use the entity records, to provide one for your system. See: https://github.com/openbmc/phosphor-host-ipmid/blob/master/scripts/entity-example.md for details on how it should be formatted. Currently formatted: [{ "id": 1, # Container entity contains other entities # Entity Id and entity Instance for the container entity "containerEntityId": 13, "containerEntityInstance": 81, # A record can have contained entities as a four entry list or as upto # two ranges of entity instances; this record has contained entities # as a four entry list "isList": true, # Records can be linked if necessary to extend the number of contained # entities within a container entity; this record is not linked "isLinked": false, "entities": [ {"entityId1": 10, "entityInstance1": 1}, {"entityId2": 10, "entityInstance2": 3}, {"entityId3": 10, "entityInstance3": 5}, {"entityId4": 10, "entityInstance4": 7} ] }] (From meta-phosphor rev: 34d8886d6642eb0b991b696f4d28950c5bec9bf5) Signed-off-by: Patrick Venture <venture@google.com> Change-Id: I00956c92d444ac82d4a9aabfd33c26ccbb58e145 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-04-23Add internal ipmi channelVernon Mauery1-4/+4
This configures a channel for the internal communication via the native D-Bus channel. This is what the internal copy of ipmitool would run commands as. So if any command run by the internal ipmitool uses the special channel 0x0E, it will be reported as 0x08 (INTRABMC). (From meta-phosphor rev: 593ac2ebb5ff779356de676865b37bd6f067b0c5) Change-Id: Ieba0af1f3f7bd5ac85df8286349170f618379756 Signed-off-by: Vernon Mauery <vernon.mauery@linux.intel.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-03-21Update the medium type & protocol for channel 0xfSuryakanth Sekar1-2/+2
According to the IPMI,channel 0xf,medium should be system-interface and protocol should be kcs. Tested: get channelInfo command should provide proper medium and protocol. Req: ipmitool raw 0x6 0x42 0xf Res: 0f <0c> <05> 00 f2 1b 0 0 0 (From meta-phosphor rev: b9d41600930802648db433b6ba48e48cab9300df) Signed-off-by: Suryakanth Sekar <suryakanth.sekar@linux.intel.com> Change-Id: I9567875e484d009cee2af1031100d83fb2d196ec Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
2019-02-04Sync channel name to network interface nameRichard Marian Thomaiyar1-2/+2
Update channel config to network interface name so that it can be referenced directly without any mapper. i.e. channel name is network interface name Depends on phosphor-host-ipmid version, which is also updated in this patch (From meta-phosphor rev: 8d2b48ddef636c8daea43111cc843ed6aaa67688) Change-Id: I3bb5780d3182cbae2a490943818f5d5d20034275 Signed-off-by: Richard Marian Thomaiyar <richard.marian.thomaiyar@linux.intel.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2018-11-08Default channel config JSON dataAppaRao Puli2-0/+194
Added default configuration JSON files for all channel information, includes 1) Channel common config 2) Channel access (volatile & non-volatile) data (From meta-phosphor rev: 549a76fc7a8e3cb0b3d84515397aa9c03786204f) Change-Id: Iad077e389fea41cd1d0bf02cef781c8314e6fcae Signed-off-by: AppaRao Puli <apparao.puli@intel.com> Signed-off-by: Richard Marian Thomaiyar <richard.marian.thomaiyar@linux.intel.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2018-09-06meta-phosphor: Move layer content from common/Brad Bishop5-0/+44
Adopt a more conventional directory hierarchy. meta-phosphor is still a _long_ way from suitable for hosting on yoctoproject.org but things like this don't help. (From meta-phosphor rev: 471cfcefa74b8c7ceb704cb670e6d915cf27c63b) Change-Id: I3f106b2f6cdc6cec734be28a6090800546f362eb Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>