Searched hist:"6 ba8d31525130dbb5ef5b60336993ef7b50a8f51" (Results 1 – 2 of 2) sorted by relevance
| /openbmc/phosphor-host-ipmid/user_channel/ |
| H A D | passwd_mgr.hpp | diff 6ba8d31525130dbb5ef5b60336993ef7b50a8f51 Fri Apr 10 13:22:50 CDT 2020 Richard Marian Thomaiyar <richard.marian.thomaiyar@linux.intel.com> [Fix]: Restrict password file permissions to 600
pam-ipmi is already updated restrict file permission of /etc/key_file
& /etc/ipmi_pass to 600 during creation. But this won't affect when firmware
is updated with nv section preserved or without user credentials getting
changed. This commit will check the file permission on every boot and update
both the files to 600.
Tested:
1. Verified that RMCP+ connection still works after this change
2. Manually set file permission to 777 and restrating ipmid or BMC
will fix the same.
Change-Id: Icfe8af5af918792412fb42e8114fcf859848e1a8
Signed-off-by: Richard Marian Thomaiyar <richard.marian.thomaiyar@linux.intel.com>
|
| H A D | passwd_mgr.cpp | diff 6ba8d31525130dbb5ef5b60336993ef7b50a8f51 Fri Apr 10 13:22:50 CDT 2020 Richard Marian Thomaiyar <richard.marian.thomaiyar@linux.intel.com> [Fix]: Restrict password file permissions to 600
pam-ipmi is already updated restrict file permission of /etc/key_file
& /etc/ipmi_pass to 600 during creation. But this won't affect when firmware
is updated with nv section preserved or without user credentials getting
changed. This commit will check the file permission on every boot and update
both the files to 600.
Tested:
1. Verified that RMCP+ connection still works after this change
2. Manually set file permission to 777 and restrating ipmid or BMC
will fix the same.
Change-Id: Icfe8af5af918792412fb42e8114fcf859848e1a8
Signed-off-by: Richard Marian Thomaiyar <richard.marian.thomaiyar@linux.intel.com>
|