/openbmc/openbmc/poky/bitbake/doc/ |
H A D | releases.rst | 1 .. SPDX-License-Identifier: CC-BY-2.5 11 - :yocto_docs:`BitBake 2.10 User Manual </bitbake/2.10/>` 17 - :yocto_docs:`BitBake 2.8 User Manual </bitbake/2.8/>` 23 - :yocto_docs:`BitBake 2.0 User Manual </bitbake/2.0/>` 33 - :yocto_docs:`BitBake 2.6 User Manual </bitbake/2.6/>` 39 - :yocto_docs:`BitBake 2.4 User Manual </bitbake/2.4/>` 45 - :yocto_docs:`BitBake 2.2 User Manual </bitbake/2.2/>` 51 - :yocto_docs:`BitBake 1.52 User Manual </bitbake/1.52/>` 57 - :yocto_docs:`BitBake 1.50 User Manual </bitbake/1.50/>` 63 - :yocto_docs:`BitBake 1.48 User Manual </bitbake/1.48/>` [all …]
|
H A D | index.rst | 1 .. SPDX-License-Identifier: CC-BY-2.5 4 BitBake User Manual 13 bitbake-user-manual/bitbake-user-manual-intro 14 bitbake-user-manual/bitbake-user-manual-execution 15 bitbake-user-manual/bitbake-user-manual-metadata 16 bitbake-user-manual/bitbake-user-manual-ref-variables-context 17 bitbake-user-manual/bitbake-user-manual-fetching 18 bitbake-user-manual/bitbake-user-manual-ref-variables 19 bitbake-user-manual/bitbake-user-manual-library-functions 20 bitbake-user-manual/bitbake-user-manual-hello [all …]
|
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/User/ |
H A D | Manager.interface.yaml | 2 Provides user management functionality. As communication to this service is 7 - name: CreateUser 9 Creates a new user. If the user already exists, then it will throw an 12 - name: UserName 15 User name which has to be created. 16 - name: GroupNames 19 List of groups to which the user has to be added. 20 - name: Privilege 23 Privilege of the user to be added. 24 - name: Enabled [all …]
|
H A D | README.md | 1 # User Management 5 User Manager service exposes D-Bus methods for user management operations. 7 ### User Manager Interface 9 User manager interface `xyz.openbmc_project.User.Manager` provides following 12 #### xyz.openbmc_project.User.Manager interface 16 - CreateUser - To create new user to the system. 17 - RenameUser - To rename existing user to new name in the system. 21 - AllGroups - To list all the groups supported in the system. 22 - AllPrivileges - To list all the privileges supported in the system. 26 - UserRenamed - Signal sent out when user is renamed in the system. [all …]
|
H A D | Common.errors.yaml | 1 # xyz.openbmc_project.User.Common.Error.UserNameExists 2 - name: UserNameExists 3 description: Specified user name already exists. 4 # xyz.openbmc_project.User.Common.Error.UserNameDoesNotExist 5 - name: UserNameDoesNotExist 6 description: Specified user name does not exist. 7 # xyz.openbmc_project.User.Common.Error.UserNameGroupFail 8 - name: UserNameGroupFail 9 description: Specified Group related restriction failure for user name. 10 # xyz.openbmc_project.User.Common.Error.UserNamePrivFail [all …]
|
H A D | TOTPAuthenticator.interface.yaml | 2 This interface defines methods and properties required for Time-based 3 One-time Password (TOTP) multi-factor authentication at user level to 4 support multi-factor authentication secret key setup for each user. This 5 interface implemented by each user object to support TOTP based 9 - name: CreateSecretKey 11 This method setup Time-based One-time Password (TOTP) authenticator 12 secret key for the given user and returns secret key string to share 13 secret key to user. 15 - name: SecretKey 18 Secret key string which will be shared to user to setup TOTP [all …]
|
H A D | Attributes.interface.yaml | 2 Provides user objects, their properties. As communication to this service is 7 - name: UserGroups 10 Groups to which the user belong. 12 - xyz.openbmc_project.Common.Error.InternalFailure 14 - name: UserPrivilege 17 Privilege of the user. Acceptable values of the system are listed 18 under AllPrivileges property under User.Manager interface. 20 - xyz.openbmc_project.Common.Error.InternalFailure 21 - xyz.openbmc_project.Common.Error.InvalidArgument 23 - name: UserEnabled [all …]
|
/openbmc/openbmc-test-automation/redfish/dmtf_tools/ |
H A D | test_redfishtool_local_user.robot | 4 Documentation Suite to test local user management. 23 ... redfishtool raw -r ${OPENBMC_HOST}:${HTTPS_PORT} -u ${OPENBMC_USERNAME} -p ${OPENBMC_PASSWORD}… 29 [Documentation] Create user via Redfishtool and verify. 31 [Teardown] Redfishtool Delete User "UserT100" 33 Redfishtool Create User "UserT100" "TestPwd123" "ReadOnly" true 34 Redfishtool Verify User "UserT100" "ReadOnly" 38 [Documentation] Modify user via Redfishtool and verify. 40 [Teardown] Redfishtool Delete User "UserT100" 42 Redfishtool Create User "UserT100" "TestPwd123" "ReadOnly" true 43 Redfishtool Update User Role "UserT100" "Administrator" [all …]
|
/openbmc/openbmc-test-automation/gui/gui_test/security_and_access_menu/ |
H A D | test_user_management_sub_menu.robot | 3 Documentation Test OpenBMC GUI "User management" sub-menu of "Security and access". 16 ${xpath_user_management_heading} //h1[text()="User management"] 17 ${xpath_select_user} //input[contains(@class,"custom-control-input")] 19 ${xpath_add_user} //button[contains(text(),'Add user')] 20 ${xpath_edit_user} //*[@data-test-id='userManagement-tableRowAction-edit-0'] 21 ${xpath_delete_user} //*[@data-test-id='userManagement-tableRowAction-delete-1'] 22 ${xpath_account_status_enabled_button} //*[@data-test-id='userManagement-radioButton-statusEnable… 23 ${xpath_account_status_disabled_button} //*[@data-test-id='userManagement-radioButton-statusDisabl… 24 ${xpath_username_input_button} //*[@data-test-id='userManagement-input-username'] 25 ${xpath_privilege_list_button} //*[@data-test-id='userManagement-select-privilege'] [all …]
|
/openbmc/docs/architecture/ |
H A D | user-management.md | 1 # User Management - OpenBMC - Design document 6 user-management components. The implementation detail is beyond the scope of 11 1. Use common user-management (e.g. phosphor-user-manager) rather than 12 application-based user-management. Especially, avoid IPMI based 13 user-management. 14 2. For security reasons, avoid transmitting passwords over any D-Bus API. 15 Observe this rule even while creating, modifying or authenticating the user. 16 3. Have applications use the PAM module to authenticate the user instead of 17 relying on a D-Bus API-based approach. 18 4. User creation has to be generic in nature wherever possible. [all …]
|
/openbmc/phosphor-host-ipmid/user_channel/ |
H A D | user_layer.hpp | 8 // http://www.apache.org/licenses/LICENSE-2.0 47 * User privilege related access data as per IPMI specification.(refer spec 71 * given user and channel. (refer spec sec 24.6) 81 /** @brief initializes user management 87 /** @brief The ipmi get user password layer call 89 * @param[in] userName - user name 98 * @param[in] userName - user name to be removed 100 * @return 0 on success, non-zero otherwise. 104 /** @brief The IPMI call to reuse password entry for the renamed user 107 * @param[in] userName - user name which has to be renamed [all …]
|
H A D | user_mgmt.hpp | 8 // http://www.apache.org/licenses/LICENSE-2.0 57 // User manager related 59 "xyz.openbmc_project.User.Manager"; 60 static constexpr const char* userMgrObjBasePath = "/xyz/openbmc_project/user"; 61 static constexpr const char* userObjBasePath = "/xyz/openbmc_project/user"; 63 "xyz.openbmc_project.User.Manager"; 65 "xyz.openbmc_project.User.Attributes"; 72 // User manager signal memebers 77 // User interface properties 83 "priv-reserved", // PRIVILEGE_RESERVED - 0 [all …]
|
/openbmc/qemu/docs/system/devices/ |
H A D | vhost-user.rst | 3 vhost-user back ends 4 -------------------- 6 vhost-user back ends are way to service the request of VirtIO devices 10 vhost-user device 15 a ``chardev`` option which specifies the ID of the ``--chardev`` 16 device that connects via a socket to the vhost-user *daemon*. 18 Each device will have an virtio-mmio and virtio-pci variant. See your 21 .. list-table:: vhost-user devices 23 :header-rows: 1 25 * - Device [all …]
|
H A D | vfio-user.rst | 1 .. SPDX-License-Identifier: GPL-2.0-or-later 4 vfio-user 7 QEMU includes a ``vfio-user`` client. The ``vfio-user`` specification allows for 9 ``vhost-user`` in this respect (see :doc:`vhost-user`), but can emulate arbitrary 11 kernel, ``vfio-user``, while similar in implementation, is handled entirely in 15 setting up a ``vfio-user`` UNIX socket between QEMU and SPDK, a VM can send NVMe 18 Presuming a suitable ``vfio-user`` server has opened a socket at 19 ``/tmp/vfio-user.sock``, a device can be configured with for example: 21 .. code-block:: console 23 -device '{"driver": "vfio-user-pci","socket": {"path": "/tmp/vfio-user.sock", "type": "unix"}}' [all …]
|
/openbmc/openbmc-test-automation/gui/test/access_control/ |
H A D | test_obmc_gui_local_users.robot | 3 Documentation Test OpenBMC GUI "Local users" sub-menu of "Access control". 14 ${xpath_select_user} //input[contains(@class,"bmc-table__checkbox-input")] 15 ${xpath_edit_user} //button[@aria-label="Edit"] 16 ${xpath_delete_user} //button[@aria-label="Delete"] 18 ${xpath_add_user} //button[text()[contains(.,"Add user")]] 29 Verify Existence Of All Sections In Local User Management Page 30 [Documentation] Verify existence of all sections in local user management page. 36 Verify Existence Of All Buttons In Local User Management Page 37 [Documentation] Verify existence of all buttons in local user management page. 46 Verify Existence Of All Input Boxes In Local User Management Page [all …]
|
/openbmc/openbmc-test-automation/redfish/account_service/ |
H A D | test_user_account.robot | 2 Documentation Test suite for verifying Redfish admin, readonly operation user accounts. 32 Verify Redfish Admin User Persistence After Reboot 33 [Documentation] Verify Redfish admin user persistence after reboot. 36 ... Redfish Create User admin_user TestPwd123 Administrator ${True} 44 Redfish Verify User admin_user TestPwd123 Administrator ${True} 47 Verify Redfish Operator User Persistence After Reboot 48 [Documentation] Verify Redfish operator user persistence after reboot. 51 ... Redfish Create User operator_user TestPwd123 Operator ${True} 59 Redfish Verify User operator_user TestPwd123 Operator ${True} 62 Verify Redfish Readonly User Persistence After Reboot [all …]
|
/openbmc/phosphor-user-manager/ |
H A D | user_mgr.hpp | 8 // http://www.apache.org/licenses/LICENSE-2.0 23 #include <phosphor-logging/elog-errors.hpp> 24 #include <phosphor-logging/elog.hpp> 25 #include <phosphor-logging/lg2.hpp> 29 #include <xyz/openbmc_project/User/AccountPolicy/server.hpp> 30 #include <xyz/openbmc_project/User/Manager/server.hpp> 31 #include <xyz/openbmc_project/User/MultiFactorAuthConfiguration/server.hpp> 32 #include <xyz/openbmc_project/User/TOTPState/server.hpp> 42 namespace user namespace 52 using UserMgrIface = sdbusplus::xyz::openbmc_project::User::server::Manager; [all …]
|
H A D | users.hpp | 8 // http://www.apache.org/licenses/LICENSE-2.0 22 #include <xyz/openbmc_project/User/Attributes/server.hpp> 23 #include <xyz/openbmc_project/User/MultiFactorAuthConfiguration/server.hpp> 24 #include <xyz/openbmc_project/User/TOTPAuthenticator/server.hpp> 27 namespace user namespace 31 using UsersIface = base::User::server::Attributes; 33 using TOTPAuthenticatorIface = base::User::server::TOTPAuthenticator; 37 using MultiFactorAuthType = sdbusplus::common::xyz::openbmc_project::user:: 40 sdbusplus::common::xyz::openbmc_project::user::MultiFactorAuthConfiguration; 41 // Place where all user objects has to be created [all …]
|
/openbmc/qemu/scripts/ |
H A D | update-syscalltbl.sh | 2 arch/alpha/kernel/syscalls/syscall.tbl,linux-user/alpha/syscall.tbl \ 3 arch/arm/tools/syscall.tbl,linux-user/arm/syscall.tbl \ 4 scripts/syscall.tbl,linux-user/aarch64/syscall_64.tbl \ 5 scripts/syscall.tbl,linux-user/hexagon/syscall.tbl \ 6 scripts/syscall.tbl,linux-user/loongarch64/syscall.tbl \ 7 arch/m68k/kernel/syscalls/syscall.tbl,linux-user/m68k/syscall.tbl \ 8 arch/microblaze/kernel/syscalls/syscall.tbl,linux-user/microblaze/syscall.tbl \ 9 arch/mips/kernel/syscalls/syscall_n32.tbl,linux-user/mips64/syscall_n32.tbl \ 10 arch/mips/kernel/syscalls/syscall_n64.tbl,linux-user/mips64/syscall_n64.tbl \ 11 arch/mips/kernel/syscalls/syscall_o32.tbl,linux-user/mips/syscall_o32.tbl \ [all …]
|
/openbmc/qemu/tests/docker/dockerfiles/ |
H A D | debian-all-test-cross.docker | 2 # Docker all cross-compiler target (tests only) 7 # to build and run linux-user tests on GitLab 9 FROM docker.io/library/debian:12-slim 11 # Duplicate deb line as deb-src 12 RUN sed -in "s/Types: deb/Types: deb deb-src/g" /etc/apt/sources.list.d/debian.sources 15 apt-get update && \ 16 apt-get install -y eatmydata && \ 17 eatmydata apt-get dist-upgrade -y && \ 18 apt build-dep -yy --arch-only qemu 22 apt install -y --no-install-recommends \ [all …]
|
/openbmc/phosphor-webui/app/access-control/controllers/ |
H A D | user-controller.js | 2 * Controller for user Accounts 4 * @module app/access-control 32 * @param {*} user 34 function checkIfRoot(user) { argument 35 return user.UserName === 'root' ? true : false; 40 * @param {*} user 41 * @returns user 43 function mapTableData(user) { argument 44 const accountStatus = user.Locked ? 'Locked' : 45 user.Enabled ? 'Enabled' : [all …]
|
/openbmc/phosphor-dbus-interfaces/gen/xyz/openbmc_project/User/ |
H A D | meson.build | 13 sdbusplus_current_path = 'xyz/openbmc_project/User' 16 'xyz/openbmc_project/User/AccountPolicy__markdown'.underscorify(), 18 '../../../../yaml/xyz/openbmc_project/User/AccountPolicy.interface.yaml', 24 '--command', 26 '--output', 28 '--tool', 30 '--directory', 32 'xyz/openbmc_project/User/AccountPolicy', 40 'xyz/openbmc_project/User/Attributes__markdown'.underscorify(), 42 '../../../../yaml/xyz/openbmc_project/User/Attributes.interface.yaml', [all …]
|
/openbmc/openbmc-test-automation/ipmi/ |
H A D | test_ipmi_payload.robot | 92 Verify Set User Access Payload For Standard Payload SOL 95 [Teardown] Run Keywords Set User Access Payload For Given User ${user_id_in_hex} 96 ... AND Delete Created User ${userid} 99 ${userid} ${username}= Create And Verify IPMI User 103 # Get default user access payload values. 104 …${default_user_access_payload}= Get User Access Payload For Given Channel ${userid_in_hex_format} 106 # Disable Standard payload 1 via set user access payload command. 107 Set User Access Payload For Given User ${user_id_in_hex} Disable 112 Verify Set User Access Payload For Operator Privileged User 113 [Documentation] Try to set user access payload using operator privileged user and expect error. [all …]
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/libconfuse/files/ |
H A D | CVE-2022-40320.patch | 6 Signed-off-by: Joachim Wiberg <troglobit@gmail.com> 8 CVE: CVE-2022-40320 9 Upstream-Status: Backport [https://github.com/libconfuse/libconfuse/commit/d73777c2c3566fb2647727bb… 10 Signed-off-by: Peter Marko <peter.marko@siemens.com> 11 --- 12 src/confuse.c | 9 ++++++--- 13 1 file changed, 6 insertions(+), 3 deletions(-) 15 diff --git a/src/confuse.c b/src/confuse.c 17 --- a/src/confuse.c 19 @@ -1872,17 +1872,20 @@ DLLIMPORT char *cfg_tilde_expand(const char *filename) [all …]
|
/openbmc/openbmc-test-automation/security/ |
H A D | test_bmc_expire_password.robot | 2 Documentation Test root user expire password. 17 # If user re-tries more than 5 time incorrectly, the user gets locked for 5 minutes. 29 [Documentation] Expire root user password and expect an error while access via IPMI. 35 ${status}= Run Keyword And Return Status Run External IPMI Standard Command lan print -v 40 [Documentation] Expire root user password and expect an error while access via SSH. 51 Expire And Change Root User Password And Access Via SSH 52 [Documentation] Expire and change root user password and access via SSH. 55 ... Restore Default Password For Root User AND FFDC On Test Case Fail 72 ... Restore Default Password For Root User AND FFDC On Test Case Fail 83 Expire And Change Root User Password Via Redfish And Verify [all …]
|