Bug 2157896 - TPM2-abrmd-selinux - Missing interface in distributed version of package
Summary: TPM2-abrmd-selinux - Missing interface in distributed version of package
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: tpm2-abrmd-selinux
Version: 38
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Javier Martinez Canillas
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 2157894
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-01-03 13:34 UTC by Patrik Koncity
Modified: 2024-09-19 04:25 UTC (History)
6 users (show)

Fixed In Version:
Clone Of: 2157894
Environment:
Last Closed: 2024-05-21 14:24:57 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Patrik Koncity 2023-01-03 13:34:38 UTC
Description of problem:
I already made for tpm2-abrmd-selinux upstream policy some improvements related of tpm2-abrmd usage with keylime. [1] Keylime should communicate with tpm2-tabrmd and need allowing rules for proper working. PR is already merged in upstream policy, but it should be good to add it into fedora distributed policy. In keylime we have now workaround solution, but for more secure policy where will be granted only needed permission should be used interfaces which were already add in tpm2-abrmd upstream. [2] [3] 


Version-Release number of selected component (if applicable):
tpm2-abrmd-selinux-2.3.1-6.fc37.src.rpm


Actual results:
In tpm2-tabrmd selinux policy now missing upstream change which allow tpm2-abrmd work with keylime.


Expected results:
Missing rules will be added to distributed tpm2-abrmd-selinux package.


[1] https://github.com/tpm2-software/tpm2-abrmd/commit/2075b8519d2e6f57807ce4df8177b31520de8f90

[2] https://github.com/RedHat-SP-Security/keylime-selinux/blob/3c23ccc63959cf60384e6b4c33b43e3335d0f4dd/keylime.te#L100

[3] https://github.com/RedHat-SP-Security/keylime-selinux/blob/3c23ccc63959cf60384e6b4c33b43e3335d0f4dd/keylime.te#L127

Comment 1 Ben Cotton 2023-02-07 15:04:32 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 38 development cycle.
Changing version to 38.

Comment 2 Patrik Koncity 2023-06-08 12:15:42 UTC
Any updates here? In downstream already landed fix.

Comment 3 Aoife Moloney 2024-05-07 15:54:41 UTC
This message is a reminder that Fedora Linux 38 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 38 on 2024-05-21.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '38'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 38 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 4 Aoife Moloney 2024-05-21 14:24:57 UTC
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21.

Fedora Linux 38 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 5 Red Hat Bugzilla 2024-09-19 04:25:13 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days


Note You need to log in before you can comment on or make changes to this bug.