[buug] ssh Question
rick at linuxmafia.com
Mon Nov 27 17:10:58 PST 2000
begin Luis quotation:
> here's the problem that I'm having, i download the ssh-1.2.30
> installed it in red hat 7.0 I have 2 linux box so both of them have
> ssh running.
> What i'm having trouble is trying to open any of the conf file from
> the terminal But the terminal that i'm trying to use is the one that
> comes with sshbuddy.
> You make connections through sshbuddy, and if you like to connect all
> you do is double click on them. it opens up a terminal for you, so
> your good to go. but when i try to open or userconf or the netconf i
> get this error message
> X11 connection rejected because of wrong authentication at Mon Nov 27
> Rejected connection at Mon Nov 27 :X11connection from linuxserver port
> Error message from remadin: Gdk-Error **: X connection to
> linuxserver:10.0 broken ( explicit kill or server shutdown)
1. Your explanation of the problem was more than a bit difficult to
2. You used the term "sshbuddy" as if it were something standard. It's
not. I know quite a lot of SSH-related software, but this is the first
I've heard of it. (I just found a description of it on a Tucows
"Linuxberg" mirror, http://linuxberg.iol.it/x11html/preview/10392.html .
It's a graphical front-end for SSH terminal sessions.)
3. Your problem would appear to be that you're trying to run some X
(graphical) client, "userconf", on the remote box, imaging it across the
network onto your local X server, _but_ have X forwarding over the SSH
In your sshd_config file, make sure you have the following lines. I'm
pretty sure you'll find they're not there:
Please see also:
(This concerns ssh.com's SSH v. 2.x, not the 1.2.30 you're running!)
NOTE: There's a reason why X forwarding over SSH is disabled by
default. It's a security risk. Besides, in the long term, you really
ought to wean yourself off X-based administrative tools.
Also, make sure you have valid DNS for the two boxes, including reverse
DNS. If you have _any doubt_ about that, or don't understand what I'm
saying, then just make sure there are entries for both machines in the
/etc/hosts files of both machines.
NOTE2: The best way to figure out SSH problems is to run the software
in debug or verbose mode, e.g., ssh with the "-v" option for the SSH
implmenetation you're using.
Cheers, "Reality is not optional."
Rick Moen -- Thomas Sowell
rick at linuxmafia.com
More information about the buug