ssh and X

[Derek Martin]

On 25 Jan 2000, Derek Atkins wrote:

> You need to copy your .Xauthority file.  This file is created at every
> login and sshd uses that to authorize X connections.  My routine is:
> 
> ssh accesshost
> ...
> accesshost% rcp .Xauthority remotehost:
> accesshost% echo $DISPLAY
> accesshost:10.0
> accesshost% rlogin remotehost
> ...
> remotehost% setenv DISPLAY accesshost:10.0
> remotehost%

No kidding?  I'm very surprised by that.  But I suppose it does make a
certain amount of sense.  The whole point is security, and xhost +
certainly doesn't provide any... :)

But what if I simultaneously am logged in on remotehost and have an active
X session?  Then my new Xauth file will overwrite my old one, and prevent
local clients from connecting, no?


-- 
"Quis custodiet ipsos custodes?"    "Who watches the watchmen?" 
-Juvenal, Satires, VI, 347 

Derek D. Martin      |  Senior UNIX Systems/Network Administrator
Arris Interactive    |  A Nortel Company
derekm at mediaone.net  |  dmartin at ne.arris-i.com
-------------------------------------------------

-
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at blu.org (Subject line is ignored).