Bug 453775

Summary: gdm should add xauth entries for network interfaces
Product: [Fedora] Fedora Reporter: Ray Strode [halfline] <rstrode>
Component: gdmAssignee: jmccann
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: 9CC: cschalle, darryl.bond, idonaldson0, rstrode, tomc
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-07-14 15:33:08 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 Ray Strode [halfline] 2008-07-02 13:47:24 UTC
From bug 446672:

-- Additional comment from dbond.au on 2008-07-02 06:26 EST --
It still won't allow using tcp sockets due to xauth.
Here is what my machine has using kdm
$ xauth list
192.168.12.100:0  MIT-MAGIC-COOKIE-1  e69ee76b144631b1f0d2495c249447fc
172.31.100.254:0  MIT-MAGIC-COOKIE-1  e69ee76b144631b1f0d2495c249447fc
192.168.122.1:0  MIT-MAGIC-COOKIE-1  e69ee76b144631b1f0d2495c249447fc
[fe80::21d:7dff:fee6:9b48]:0  MIT-MAGIC-COOKIE-1  e69ee76b144631b1f0d2495c249447fc
[fe80::248:54ff:fe3f:5bed]:0  MIT-MAGIC-COOKIE-1  e69ee76b144631b1f0d2495c249447fc
[fe80::c8ec:18ff:fe37:eb42]:0  MIT-MAGIC-COOKIE-1  e69ee76b144631b1f0d2495c249447fc
[fe80::984e:e0ff:fe64:4dbd]:0  MIT-MAGIC-COOKIE-1  e69ee76b144631b1f0d2495c249447fc
gold/unix:0  MIT-MAGIC-COOKIE-1  e69ee76b144631b1f0d2495c249447fc

Using gdm, only the last line (ie unix sockets).

Comment 1 Ian Donaldson 2009-02-16 08:02:14 UTC
Any updates to this?  I'm using FC10 and have added 

[security]
DisallowTCP=false

to /etc/gdm/custom.conf 

but nothing is creating a cookie for the IP ...

(I'm using kde4.2.0)

Related, I also note that the environment contains:

XAUTHORITY=/var/run/gdm/auth-for-iand-nfY6vS/database

and that authority file contains only the unix domain authority entry.

Seems to me that XAUTHORITY shouldn't be set by the time that clients
start, so that $HOME/.Xauthority is used, and the keys from gdm
should me merged into $HOME/.Xauthority at login time.

Comment 2 Bug Zapper 2009-06-10 01:53:14 UTC
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '9'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 9 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Bug Zapper 2009-07-14 15:33:08 UTC
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.