-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
rhel-9.1.0
-
None
-
Moderate
-
rhel-sst-kernel-security
-
ssg_core_kernel
-
None
-
False
-
-
None
-
None
-
None
-
None
-
If docs needed, set a value
-
-
Unspecified
-
None
Description of problem:
When configuring IMA/EVM and importing a key to the IMA keyring, while the key can be successfully imported, said key is unable to be used with any self-signed RPM packages that has the key's respective certificate.
Version-Release number of selected component (if applicable):
libattr-2.5.1-3.el9.x86_64
attr-2.5.1-3.el9.x86_64
ima-evm-utils-1.4-4.el9.x86_64
keyutils-libs-1.6.3-1.el9.x86_64
keyutils-1.6.3-1.el9.x86_64
How reproducible:
Consistently
Steps to Reproduce:
1. Implement IMA/EVM via documentation (see Additional Info).
2. Create key and respective self-signed certificate.
3. Create RPM package and sign with certificate.
4. Import key to IMA keyring.
5. Attempt to install self-signed RPM.
Actual results:
Imported key is able to be utilized on it's respective self-signed RPM package.
Expected results:
Imported key is unable to be utilized on it's respective self-signed RPM package.
Additional info:
Documentation referenced is the following:
- external trackers