Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
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 10Zbigniew 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.
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