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 1658642 - Store user runtime files in /run/user/ rather than in /tmp/
Summary: Store user runtime files in /run/user/ rather than in /tmp/
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: openssh
Version: 8.0
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: rc
: 8.1
Assignee: Dmitry Belyavskiy
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On: 1682500
Blocks: 1654830
TreeView+ depends on / blocked
 
Reported: 2018-12-12 15:25 UTC by Jakub Jelen
Modified: 2024-06-13 22:01 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-01-18 17:07:08 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenSSH Project 2950 0 None None None 2019-07-02 11:46:36 UTC

Description Jakub Jelen 2018-12-12 15:25:31 UTC
Based on the discussion in the bug #1654830, we should make OpenSSH using the /run/user directory for the things that belong there, namely:

 * The location of file with information about authentication
 * The default location of the ssh-agent socket (in Gnome, gnome-keyring is already taking the socket here)
 * The default location of the forwarded kerberos credential cache
 * The location of the forwarded ssh-agent socket

The issue with using /tmp is mostly when the tmpfs is full, which can produce unexpected behavior (failing agent forwarding, kerberos authentication ...)

The upstream acceptance is questionable (it is systemd), but with proper configure checks, it should be possible to implement it in a clean and portable way.

I assume OpenSSH should claim the /run/user/EUID/openssh/ directory, where the separate temporary files should be placed.

Comment 1 Jakub Jelen 2019-01-04 16:25:06 UTC
I submitted the upstream bug with a patch. Expanded commits are available here:

https://github.com/openssh/openssh-portable/compare/master...Jakuje:run-user

I would be happy for feedback or testing.

Comment 2 Pat Riehecky 2019-01-04 17:12:36 UTC
Would this also capture the GSSAPI/Kerberos ticket forwarding or does that happen down in the krb5 libs (/tmp/krb5cc_1000_15475)?

Comment 3 Jakub Jelen 2019-01-07 09:20:24 UTC
Yes, this captures also the kerberos tickets, as mentioned in the bug description:

  https://github.com/openssh/openssh-portable/compare/master...Jakuje:run-user#diff-17b3a83e02209e8b555ed4893c1abe25R252

We already carry in the RHEL patches to be able to configure the location of the kerberos tickets in krb5.conf, but if this file does not provide any guidance, the OpenSSH falls back to the default (with this patch, it would be /run/user/...).


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