Date: Wed, 5 Jul 2000 21:07:16 -0700 From: "Crist J. Clark" <cristjc@earthlink.net> To: Ted Faber <faber@ISI.EDU> Cc: Kevin Oberman <oberman@es.net>, Jason Fesler <jfesler@gigo.com>, Harry Putnam <reader@newsguy.com>, freebsd-mobile@FreeBSD.ORG Subject: Re: X-display from laptop to desk Message-ID: <20000705210716.A631@dialin-client.earthlink.net> In-Reply-To: <200007051653.JAA01200@ted.isi.edu>; from faber@ISI.EDU on Wed, Jul 05, 2000 at 09:53:57AM -0700 References: <200007031924.e63JOqn08344@ptavv.es.net> <200007051653.JAA01200@ted.isi.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jul 05, 2000 at 09:53:57AM -0700, Ted Faber wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Content-Type: text/plain; charset=us-ascii > > "Kevin Oberman" wrote: > > > >A better solution to this is to redefine the XAUTHORITY variable > >to point at your X login .Xauthority file. > > > >For sh and sons: > >XAUTHORITY=/home/jfesler/.Xauthroity > >export XAUTHORITY > > > >For csh and children: > >setenv XAUTHORITY ~jfesler/.Xauthority > > This will break X11 forwarding under OpenSSH (even if you don't drag > root into it). OpenSSH creates its own xauthority file in /tmp and > points the XAUTHORITY envronment variable at it. I spent a whole day > figuring out that setting XAUTHORITY manually in my .bashrc was my > problem. I would recommend checking to see if XAUTHORITY is set first > and initializing it to $HOME/.Xauthority only if no other program has > set it. Resetting XAUTHORITY under ssh is perilous. Note that this > will break X11 forwarding under the same login. > > (Under the ssh-1.2.27 port, setting XAUTHORITY is fine, but the future > is OpenSSh on FreeBSD.) I thought that using X and su through ssh "just worked" now-a-days. I remember the problem happening to me and I had been trying to figure out how I fixed it. I _thought_ that it had just started working when I switched to the OpenSSH port and then to the OpenSSH in the base 4.0 systems. But I could swear that one of the people early on in the thread said that he was using FreeBSD 4.0 and having the problem. Does this "just work" with OpenSSH or did I fix it and forget how? -- Crist J. Clark cjclark@alum.mit.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000705210716.A631>