From owner-freebsd-questions Wed May 21 10:31:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA22667 for questions-outgoing; Wed, 21 May 1997 10:31:18 -0700 (PDT) Received: from labs.usn.blaze.net.au (labs.usn.blaze.net.au [203.17.53.30]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA22661 for ; Wed, 21 May 1997 10:31:13 -0700 (PDT) Received: from labs.usn.blaze.net.au (local [127.0.0.1]) by labs.usn.blaze.net.au (8.8.5/8.8.5) with ESMTP id DAA01041; Thu, 22 May 1997 03:29:45 +1000 (EST) Message-Id: <199705211729.DAA01041@labs.usn.blaze.net.au> X-Mailer: exmh version 2.0gamma 1/27/96 To: "P. van Leeuwen" Cc: freebsd-questions@freebsd.org Subject: Re: Xauthority In-reply-to: Your message of "Wed, 21 May 1997 15:51:16 +0200." <199705211351.PAA00530@pc-pvl.nanoteq.co.za> X-Face: (W@z~5kg?"+5?!2kHP)+l369.~a@oTl^8l87|/s8"EH?Uk~P#N+Ec~Z&@;'LL!;3?y Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 22 May 1997 03:29:44 +1000 From: David Nugent Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I managed to screw the xauthority on my machine in some way. > I noticed that exmh's background process stopped working. My > .xsession-errors show the following : > BgRegister X server insecure (must use xauth-style authorization); > command ignored > exmh-bg cannot rendez-vous with UI - exiting. ~ > I did RTFM, and checked all the xdm config files as well as > my ~/Xauthority and everything checks out. .Xauthority is created by xdm, and is refreshed on each login (you can add your owm 'private' entries too and they are correctly preserved between sessions, which is useful for xemacs, for example, but this is beside the point for now :-)). Make sure its permissions allow reading only by the user. > Unsecure display 0: > > Earlier on it said Secure though. Add "xhost -" in your .xsession. > My ~/Xauthority is empty when X isn't running and contains 2 > entries when I start xdm. That looks to be working correctly. Are the permissions ok? Other than that, adding the "xhost -" to turn off insecure connections should do the rest (it should default to that, but sometimes doesn't - I have no idea what changes it). > No other programs except tk stuff complain about anything such > as opening the display. That's because they're not insisting on using xauth, but probably fall back to using xhost, which is far too simple an authorisation protocol to be used on any internet connected machine without at least a firewall. > Does anyone have any idea what I did or how to fix it? Xauth is a pita. It should be easier than it is, or at least the error messages and documentation could be more helpful by providing some working examples. I still haven't managed to figure out how to get xauthority working with xinit, and I'd honestly prefer to startup X when I need it rather than having to use xdm. Regards, David David Nugent - Unique Computing Pty Ltd - Melbourne, Australia Voice +61-3-9791-9547 Data/BBS +61-3-9792-3507 3:632/348@fidonet davidn@freebsd.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/