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.

Bug 909790

Summary:	ssh -Y fails from remote GDM session
Product:	Red Hat Enterprise Linux 6	Reporter:	Brian Hinz <bphinz>
Component:	xorg-x11-xauth	Assignee:	Hans de Goede <hdegoede>
Status:	CLOSED ERRATA	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.3	CC:	tpelka
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	xorg-x11-xauth-1.0.9-1.el6	Doc Type:	Bug Fix
Doc Text:	Cause: xauth does not know how to deal with MIT cookies of type FamilyWild Consequence: When using a remote (xdmcp) gdm session and then doing "ssh -X" the following warning is printed: "Warning: No xauth data; using fake authentication data for X11 forwarding." and X apps started from within the ssh session will not work. Fix: Teach xauth how to deal with FamilyWild MIT cookies. Result: "ssh -X" from within a remote gdm session works as expected.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-05-10 19:16:06 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Brian Hinz 2013-02-11 02:58:11 UTC

Description of problem:
Bug 505545 is applicable to EL6.  Either (or both) of the solutions discussed there should be applied to EL6.

Version-Release number of selected component (if applicable):
xorg-x11-xauth-1.0.2-7.1.el6

How reproducible:


Steps to Reproduce:
See 505545
  
Actual results:
See 505545

Expected results:
See 505545

Additional info:
The patch to xauth alone resolved the problem to my satisfaction.

Comment 2 RHEL Program Management 2013-10-13 23:57:54 UTC

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.

Comment 4 Hans de Goede 2015-11-16 10:41:28 UTC

The planned xorg-x11-xauth rebase for 6.8 (bug 1246430), will bring in the upstream fix for this, adding devel-ack.

Comment 8 errata-xmlrpc 2016-05-10 19:16:06 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, 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://rhn.redhat.com/errata/RHBA-2016-0736.html