Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 60982

Summary:	openssh-3.1p1-2 and X11 forwarding over IPv6
Product:	[Retired] Red Hat Linux	Reporter:	Per Steinar Iversen <persteinar.iversen>
Component:	openssh	Assignee:	Tomas Mraz <tmraz>
Status:	CLOSED WORKSFORME	QA Contact:	Brian Brock <bbrock>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.2	CC:	kad, s353996
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-03-31 12:06:24 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Per Steinar Iversen 2002-03-11 09:50:39 UTC

Description of Problem:

Openssh-3.1p1-2 does not do X11 forwarding on servers that supports both IPv4
and IPv6.

Version-Release number of selected component (if applicable):

openssh-3.1p1-2 

How Reproducible:

Always

Steps to Reproduce:
1. Upgrade to openssh-3.1p1-2
2. Login by ssh
3. Try to open an xterm window

Actual Results:

Get this error message:

Warning: This program is an suid-root program or is being run by the root user.
The full text of the error or warning message cannot be safely formatted
in this environment. You may get a more descriptive message by running the
program as a non-root user or by removing the suid bit on the executable.
xterm Xt error: Can't open display: %s


Expected Results:

An xterm windows should appear.

Additional Information:
	
Using lsof and strace it is clear that openssh X11 forwarding happens locally
over 127.0.0.1 while openssh only listens on ::1 if IPv6 is available.

A simple way to get X11 forwarding to work is to start sshd with the -4 option.
Previous versions of openssh did not have this problem.

Comment 1 Tomas Mraz 2005-02-03 12:05:20 UTC

Does it still happen with current Fedora Core?

Comment 2 Tomas Mraz 2005-02-03 13:03:38 UTC

*** Bug 65543 has been marked as a duplicate of this bug. ***

Comment 3 Tomas Mraz 2005-03-31 12:06:24 UTC

No response, please reopen if still happens with a current FC/RHEL release.