Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!gem.mps.ohio-state.edu!uwm.edu!lll-winken!gauss.llnl.gov!casey
From: casey@gauss.llnl.gov (Casey Leedom)
Newsgroups: comp.windows.x
Subject: Re: GraphOn OptiMax 200 X terminal questions and answers
Keywords: X11, X terminals, high speed modems
Message-ID: <38379@lll-winken.LLNL.GOV>
Date: 14 Nov 89 01:01:42 GMT
References: <38226@lll-winken.LLNL.GOV> <38146@lll-winken.LLNL.GOV> <12382@ulysses.homer.nj.att.com> <293@ark1.nswc.navy.mil>
Sender: usenet@lll-winken.LLNL.GOV
Reply-To: casey@lll-crg.llnl.gov (Casey Leedom)
Organization: Lawrence Livermore National Laboratory
Lines: 29

| From: Dave Sill <dsill@relay.nswc.navy.mil>
| 
| But then how do you know what display number Joe Blow is using?  With the
| current UID scheme, I know Joe's UID, and which machine his
| pseudo-server's running on, e.g., UID=200, machine=foo, so
| display=foo:200.

  I have the following in my .xinitrc:

	RDISPLAY=`hostname`:`echo $DISPLAY | sed 's/unix://'`
	export RDISPLAY

I then use ``-display $RDISPLAY'' in my .uwmrc whenever I'm rsh'ing an X
command on a remote host.  As for someone else randomly instigating a
connection to your server ...  I'm not at all sure that's something we
want to encourage.  We've already got enough security problems in X as it
is.  I'd say that you want to do something like handing a remote process
a capability which both informs the remote process of how to address you
correctly and provides authorization to use the server.

| > If you have a standard login account for use by multiple
| > logins, you'd get an immediate display number collision.
| 
| Then you just revert to finding the next unused display number.

  Then we have the same problem you worried about in the first paragraph,
so we may as well just deal with the problem.

Casey