On Wed, 16 Aug 2000, Christophe TROESTLER wrote: > Well, in the meantime I restarted the X server -- needed to do some > real work[tm]! I send nonetheless the info -- if you can spot > something wrong... > > $ xauth list > aiglenoir/unix:0 MIT-MAGIC-COOKIE-1 17afba42b84d5952fce82446e7c3698e > aiglenoir/unix:0 XDM-AUTHORIZATION-1 ac717264e0f57700005dbd46e0d077fc > jedi.bxlug.be/unix:0 MIT-MAGIC-COOKIE-1 7d266805540e68476949767906173b49 > aiglenoir.linkline.be/unix:0 MIT-MAGIC-COOKIE-1 > 0f16461a07352472131746616c611009 > 212.35.0.45:0 MIT-MAGIC-COOKIE-1 4f12270b6423265d2d7e0946651b1a57 > localhost.localdomain/unix:0 MIT-MAGIC-COOKIE-1 > b8c32f12b2647caeba036f823fcfe0c6 > aiglenoir:0 MIT-MAGIC-COOKIE-1 c65f970f57b10a2767d8a0ef360f31b2
Sorry, I should have told you to censor the keys, because they are sensitive info. :-( For your safety, I strongly recommend restarting the X server on *all* machines mentioned in your listing (if you haven't done yet after "xauth list"). I'm still using slink, but I had a similar problem with some unofficial X packages. I wasn't able to figure out what the problem was, so I reverted to official slink X packages. I suppose it had something to do with confusion about plaintext (MIT-MAGIC-COOKIE-1) vs. DES (XDM-AUTHORIZATION-1) authorization. Are you using xdm? Then you might also want to check xauth -f /var/lib/xdm/authdir/authfiles/YOUR_FILENAME list and compare the key(s) to your "xauth list" output. You can find out the filename this way: ps auxw | grep "X.*-auth" it's after the -auth command line option to your X server. If you need to post keys again, please cut them to 3..4 digits or send them through md5sum: echo <key> | md5sum but do so consistently. The important diagnostic info is whether keys are the same, not their actual value. Otherwise, I'm afraid I can't be of much help. Maybe someone with more eXperience could take over. Mirko
