RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2044486 - [spec] keyctl read or revoke fail with access denied , when try to retrive the previous key added from the same user
Summary: [spec] keyctl read or revoke fail with access denied , when try to retrive th...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: systemd
Version: 9.2
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: rc
: ---
Assignee: Jan Macku
QA Contact: Frantisek Sumsal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-24 17:04 UTC by Giancarlo del Rossi
Modified: 2023-11-07 11:30 UTC (History)
13 users (show)

Fixed In Version: systemd-252-16.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-11-07 08:54:03 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gitlab redhat/centos-stream/rpms systemd merge_requests 80 0 None opened pam: add pam_keyinit.so to systemd-user 2023-06-27 12:46:04 UTC
Red Hat Issue Tracker RHELPLAN-109423 0 None None None 2022-01-24 17:13:27 UTC
Red Hat Knowledge Base (Solution) 6809451 0 None None None 2022-05-12 01:36:59 UTC
Red Hat Product Errata RHBA-2023:6640 0 None None None 2023-11-07 08:54:28 UTC

Comment 9 Michal Sekletar 2022-11-04 17:33:10 UTC 
This is caused by packaging error in systemd. We ship outdated systemd-user config file which doesn't call pam_keyinit.so. Hence gnome-terminal-server.service user service inherits session keyring from systemd --user instance which gets has KeyringMode=private (i.e. new session keyring not linked with user keyring). If pam_keyinit.so was invoked from systemd-user then this private keyring (setup by PID 1 when starting user instance) would be linked to user keyring and that is then inherited by gnome-terminal.
Comment 10 Zbigniew Jędrzejewski-Szmek 2022-11-23 15:14:42 UTC 
We discussed this during a meeting with PAM maintainers today… The issue is even more subtle:
we call 'pam_keyinit revoke' via the shared configuration, but we need to call 'pam_keyinit force revoke'.
This will need to be done in our own config. As Michal wrote, this is already done upstream,
so the fix will be to just make sure that those upstream changes are present in our downstream
version of this file.
Comment 12 Jan Macku 2023-06-27 12:46:04 UTC 
I have posted MR fixing this issue, thank you for your patience.

https://gitlab.com/redhat/centos-stream/rpms/systemd/-/merge_requests/80
Comment 16 errata-xmlrpc 2023-11-07 08:54:03 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (systemd bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:6640
Note You need to log in before you can comment on or make changes to this bug.