From owner-freebsd-questions Tue Sep 22 12:45:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA14258 for freebsd-questions-outgoing; Tue, 22 Sep 1998 12:45:34 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from berry.cs.brandeis.edu (berry.cs.brandeis.edu [129.64.2.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA14242 for ; Tue, 22 Sep 1998 12:45:22 -0700 (PDT) (envelope-from waterman@cs.brandeis.edu) Received: from home (mg136-058.ricochet.net [204.179.136.58]) by berry.cs.brandeis.edu (8.8.8/8.8.8) with ESMTP id PAA00431; Tue, 22 Sep 1998 15:44:40 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by home (8.8.8/8.8.8) with ESMTP id MAA02320; Tue, 22 Sep 1998 12:46:00 -0700 (PDT) (envelope-from waterman@home) Message-Id: <199809221946.MAA02320@home> To: dallas.tx@airmail.net cc: freebsd-questions@FreeBSD.ORG Subject: Re: Xwindows from remote In-Reply-To: Your message of "Tue, 22 Sep 1998 12:34:31 CDT." References: Reply-To: waterman@acm.org Date: Tue, 22 Sep 1998 12:46:00 -0700 From: TS Waterman Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG XFree86 is typically set up (by default, anyway) to use the Xauthority authentication shceme, usually with the MIT_MAGIC_COOKIE stuff. Take a look at the 'xauth' man page. What you'll probalby have to do is rsh (or ssh) to tabletop, and do a 'xauth list' there, then set the magic cookie on stumbleinn with 'xauth set'. You might right a tcl or perl script to grab the relevant stuff and set it on the non-X machine. The cookies are usually kept in a .Xauthority file in the home directory of whoever startup the X server, so you need the capability to read that file one way or another in order to use the display. Another security scheme that might be used is the 'xhosts' protocol, which uses a file '.xhosts' in the X-server owner's home directory much like the .rhosts file. This is a less secure protocol. These X permissions can mess you up even if you're just on one machine, but have su'd to be various users (operator, postgres admin, etc.). Even though you may have xterms or whatever running as these users, they won't be able to open anything new on the display until you set their xauth cookies. Good luck, --ts "David L. Vondrasek" writes: >OK I have a question I'm sure one of you can answer I hope. >I'm loged in to my 2.2.7 box (-tabletop- 10.124.239.13 ) under X >(AfterStep) and open a xterm and telnet to another box on the local >network (-stumbleinn- 10.124.239.12). on .12 I issue this command to set >the display env ( I think it's correct ) > >setenv DISPLAY 10.124.239.13:0.0 > >(I have it as a alais so all I do is type 'mx' ) I use it to run a WIN >X-server on -tabletop- when it's under a Windows XSERVER and it works. > > >But, when I try to run a X program on -stumbleinn- I get this error. > >------------------------- > >david@stumbleinn:/home/david : xsysinfo & >[1] 8078 >david@stumbleinn:/home/david : Xlib: connection to "10.124.239.13:0.0" >refused by server >Xlib: Client is not authorized to connect to Server >Error: Can't open display: 10.124.239.13:0.0 > >[1] Exit 1 xsysinfo >david@stumbleinn:/home/david : > >----------- >I thought it had something to do with the .rhosts on -tabletop- I mat be >wrong here.(advanced newbie) This is my .rhosts on -tabletop- > >david@tabletop:/home/david : more .rhosts ># $Id: dot.rhosts,v 1.3 1996/09/21 21:35:47 wosch Exp $ ># ># .rhosts - trusted remote host name and user data base ># ># see hosts.equiv(5), rsh(1), rlogin(1), rcp(1) ># ># This file should NOT be group or other readable. > stumbleinn.dyn.ml.org > stumbleinn > stumbleinn david ># OtherMachine myFriend > > >-------------------- > >Help ? > > > >--- >---------------------------------- >E-Mail: David L. Vondrasek >Date: 22-Sep-98 >Time: 12:34:31 > >---------------------------------- > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message