Re: [gentoo-user] X-forwarding fails with Invalid MIT-MAGIC-COOKIE-1 key

2009-04-26 Thread pk
Grant wrote:
 X-forwarding used to work for me but I haven't used it in a while and now I 
 get:
 
 Warning: untrusted X11 forwarding setup failed: xauth key data not generated
 Warning: No xauth data; using fake authentication data for X11 forwarding.
 Xlib: connection to localhost:10.0 refused by server
 Xlib: Invalid MIT-MAGIC-COOKIE-1 key
 Cannot open display:
 
 I have:
 
 # cat /etc/ssh/sshd_config | grep X11Forwarding
 X11Forwarding yes
 
 Does anyone know how to fix this?

Before using ssh (i.e. telnet, rsh and the likes) one had to manually
copy the mmc using: xauth extract - $DISPLAY | rsh otherhost xauth
merge - or something similar (i.e. the Xforwarding mechanism relies on
that the display that you want use have an identical mmc in the user
directory on the remote machine). The message Warning: No xauth
data... seems to indicate it's not creating a .Xauthority (=mmc) file
or an invalid one.

Further reading:
http://x2x.dottedmag.net/wiki/MIT-MAGIC-COOKIE-1

Hope this helps...

Best regards

Peter K



Re: [gentoo-user] X-forwarding fails with Invalid MIT-MAGIC-COOKIE-1 key

2009-04-25 Thread Grant
 X-forwarding used to work for me but I haven't used it in a while and now
 I get:

 Warning: untrusted X11 forwarding setup failed: xauth key data not
 generated
 Warning: No xauth data; using fake authentication data for X11 forwarding.
 Xlib: connection to localhost:10.0 refused by server
 Xlib: Invalid MIT-MAGIC-COOKIE-1 key
 Cannot open display:

 Ah, I had this problem for months; it was driving me crazy!

 I don't remember the specifics, but it had to to with some wankery of glibc
 not working properly with xauth.  I'm pretty sure the fix is to update to
=sys-libs/glibc-2.9_p20081201-r2 or regress glibc back a few ticks.

 Regards,
 Wyatt

Thanks Wyatt.  I upgraded the server and client to the latest glibc in
portage with the same result.  When I tried to downgrade glibc, I got:

 * Sanity check to keep you from breaking your system:
 *  Downgrading glibc is not supported and a sure way to destruction

- Grant



Re: [gentoo-user] X-forwarding fails with Invalid MIT-MAGIC-COOKIE-1 key

2009-04-25 Thread Mike Kazantsev
On Fri, 24 Apr 2009 08:01:59 -0700
Grant emailgr...@gmail.com wrote:

 X-forwarding used to work for me but I haven't used it in a while and now I 
 get:
 
 Warning: untrusted X11 forwarding setup failed: xauth key data not generated
 Warning: No xauth data; using fake authentication data for X11 forwarding.
 Xlib: connection to localhost:10.0 refused by server
 Xlib: Invalid MIT-MAGIC-COOKIE-1 key
 Cannot open display:
 
 I have:
 
 # cat /etc/ssh/sshd_config | grep X11Forwarding
 X11Forwarding yes
 
 Does anyone know how to fix this?

I remember fixing similar problem with xhost +localhost line.
Don't really remember why it helped, since I lack basic knowledge of X
authentication mechanisms.

-- 
Mike Kazantsev // fraggod.net


signature.asc
Description: PGP signature


Re: [gentoo-user] X-forwarding fails with Invalid MIT-MAGIC-COOKIE-1 key

2009-04-25 Thread Alan McKinnon
On Saturday 25 April 2009 19:25:26 Grant wrote:
  X-forwarding used to work for me but I haven't used it in a while and
  now I get:
 
  Warning: untrusted X11 forwarding setup failed: xauth key data not
  generated
  Warning: No xauth data; using fake authentication data for X11
  forwarding. Xlib: connection to localhost:10.0 refused by server
  Xlib: Invalid MIT-MAGIC-COOKIE-1 key
  Cannot open display:
 
  Ah, I had this problem for months; it was driving me crazy!
 
  I don't remember the specifics, but it had to to with some wankery of
  glibc not working properly with xauth.  I'm pretty sure the fix is to
  update to
 
 =sys-libs/glibc-2.9_p20081201-r2 or regress glibc back a few ticks.
 
  Regards,
  Wyatt

 Thanks Wyatt.  I upgraded the server and client to the latest glibc in
 portage with the same result.  When I tried to downgrade glibc, I got:

  * Sanity check to keep you from breaking your system:
  *  Downgrading glibc is not supported and a sure way to destruction

And there's a very good reason for that message - I'm sure you can figure it 
out. However, some downgrades are safe. You should be able to get away with 
downgrading to any lower version in the same minor release - 2.9 in your case.

Tip: quickpkg glibc, portage, python, gcc and other vital stuff befoore you 
try this stunt:

Edit the desired build, and look for this in pkg_setup():

if has_version ''${CATEGORY}/${PF} ; then
eerror Sanity check to keep you from breaking your system:
eerror  Downgrading glibc is not supported and a sure way to 
destruction
die aborting to save your system
fi

Comment out the die call, re-digest, re-emerge.

The very very latest ebuild has it in files/eblits/pkg_setup.eblit instead, 
but you won't be using that for a downgrade.

-- 
alan dot mckinnon at gmail dot com



[gentoo-user] X-forwarding fails with Invalid MIT-MAGIC-COOKIE-1 key

2009-04-24 Thread Grant
X-forwarding used to work for me but I haven't used it in a while and now I get:

Warning: untrusted X11 forwarding setup failed: xauth key data not generated
Warning: No xauth data; using fake authentication data for X11 forwarding.
Xlib: connection to localhost:10.0 refused by server
Xlib: Invalid MIT-MAGIC-COOKIE-1 key
Cannot open display:

I have:

# cat /etc/ssh/sshd_config | grep X11Forwarding
X11Forwarding yes

Does anyone know how to fix this?

- Grant



Re: [gentoo-user] X-forwarding fails with Invalid MIT-MAGIC-COOKIE-1 key

2009-04-24 Thread Wyatt Epp
On Fri, Apr 24, 2009 at 11:01 AM, Grant emailgr...@gmail.com wrote:

 X-forwarding used to work for me but I haven't used it in a while and now I
 get:

 Warning: untrusted X11 forwarding setup failed: xauth key data not
 generated
 Warning: No xauth data; using fake authentication data for X11 forwarding.
 Xlib: connection to localhost:10.0 refused by server
 Xlib: Invalid MIT-MAGIC-COOKIE-1 key
 Cannot open display:


Ah, I had this problem for months; it was driving me crazy!

I don't remember the specifics, but it had to to with some wankery of glibc
not working properly with xauth.  I'm pretty sure the fix is to update to
=sys-libs/glibc-2.9_p20081201-r2 or regress glibc back a few ticks.

Regards,
Wyatt