Re: x-forwarding with ssh
Tried the -v option & all seemd OK. (listed below) It seems to be
allowing X.
However it still isn't functioning.
Sorry for the delay, I decided it might be policy to upgrade the
server to Woody before carrying on but the only difference in this
context is the error message now no longer says error 101
Is it something else altogether?
Steve
debug1: Applying options for *
debug1: Seeding random number generator
debug1: Rhosts Authentication disabled, originating port will not be trusted.
debug1: restore_uid
debug1: ssh_connect: getuid 1000 geteuid 0 anon 1
debug1: Connecting to gateway [192.168.0.9] port 22.
debug1: temporarily_use_uid: 1000/1000 (e=0)
debug1: restore_uid
debug1: temporarily_use_uid: 1000/1000 (e=0)
debug1: restore_uid
debug1: Connection established.
debug1: read PEM private key done: type DSA
debug1: read PEM private key done: type RSA
debug1: identity file /home/steve/.ssh/id_rsa type -1
debug1: identity file /home/steve/.ssh/id_dsa type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_3.0.2p1 Debian 1:3.0.2p1-6
debug1: match: OpenSSH_3.0.2p1 Debian 1:3.0.2p1-6 pat ^OpenSSH
Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_3.0.2p1 Debian 1:3.0.2p1-6
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-cbc hmac-md5 none
debug1: kex: client->server aes128-cbc hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: dh_gen_key: priv key bits set: 121/256
debug1: bits set: 1614/3191
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host 'gateway' is known and matches the RSA host key.
debug1: Found key in /home/steve/.ssh/known_hosts:3
debug1: bits set: 1566/3191
debug1: ssh_rsa_verify: signature correct
debug1: kex_derive_keys
debug1: newkeys: mode 1
debug1: SSH2_MSG_NEWKEYS sent
debug1: waiting for SSH2_MSG_NEWKEYS
debug1: newkeys: mode 0
debug1: SSH2_MSG_NEWKEYS received
debug1: done: ssh_kex2.
debug1: send SSH2_MSG_SERVICE_REQUEST
debug1: service_accept: ssh-userauth
debug1: got SSH2_MSG_SERVICE_ACCEPT
debug1: authentications that can continue: publickey,password,keyboard-interactive
debug1: next auth method to try is publickey
debug1: try privkey: /home/steve/.ssh/id_rsa
debug1: try privkey: /home/steve/.ssh/id_dsa
debug1: next auth method to try is keyboard-interactive
Password:
debug1: packet_send2: adding 32 (len 20 padlen 12 extra_pad 64)
debug1: ssh-userauth2 successful: method keyboard-interactive
debug1: channel 0: new [client-session]
debug1: send channel open 0
debug1: Entering interactive session.
debug1: ssh_session2_setup: id 0
debug1: Requesting X11 forwarding with authentication spoofing.
debug1: Requesting authentication agent forwarding.
debug1: channel request 0: shell
debug1: channel 0: open confirm rwindow 0 rmax 16384
Last login: Mon Mar 4 20:26:57 2002 from rm.kingswayelec.co.uk.0.168.192.in-addr.arpa on pts/1
Linux gateway 2.2.19pre17 #1 Tue Mar 13 22:37:59 EST 2001 i586 unknown
You have mail.
Last login: Tue Mar 5 08:32:53 2002 from rm.kingswayelec.co.uk.0.168.192.in-addr.arpa
steve@gateway:~$ xterm -v
XFree86 4.1.0(165)
steve@gateway:~$ xterm
xterm Xt error: Can't open display:
steve@gateway:~$ vncviewer
Error: Can't open display:
steve@gateway:~$
On Fri, Mar 01, 2002 at 07:56:34AM -0500, Andrew Perrin wrote:
> Try the -v flag to ssh to see what it's trying to do:
>
> ssh -v -X remote.host
>
> this will let you watch the steps ssh is going through to try to debug the
> connection.
>
> If the remote host is configured correctly to allow X forwarding, you will
> not have to set DISPLAY. Setting DISPLAY to local:0.0 will make the ssh
> connection useless, since your X packets will not be tunnelled through it.
>
> ap
>
> ----------------------------------------------------------------------
> Andrew J Perrin - andrew_perrin@unc.edu - http://www.unc.edu/~aperrin
> Assistant Professor of Sociology, U of North Carolina, Chapel Hill
> 269 Hamilton Hall, CB#3210, Chapel Hill, NC 27599-3210 USA
>
>
> On Fri, 1 Mar 2002, steve downes wrote:
>
> > Tried everything in this thread (& more besides)but the closest I get
> > is:-
> >
> > steve@fileserver:~$ xterm &
> > [1] 19419
> > steve@fileserver:~$ _X11TransSocketINETConnect: Can't connect: errno = 101
> > xterm Xt error: Can't open display: fileserver:10.0
> >
> >
> >
> > I have opened X11 in ssh_config & sshd_config in both fileserver & desktop
> > I have tried -X in the ssh command & not.
> > I have opened xhost & closed it
> >
> >
> >
> > The annoying thing is in Potato it worked fine it is only since the
> > upgrade to ssh2. (upgraded both ends to ssh2 as well)
> >
> > Any more ideas?
> >
> > Steve
> >
> >
> > On Fri, Mar 01, 2002 at 04:08:42PM +1000, john wrote:
> > > Nick Wright wrote:
> > >
> > > > Hi there.
> > > >
> > > > Currently when I try to run X apps via an ssh login I get the error message
> > > >
> > > > xterm Xt error: Can't open display:
> > > >
> > > > Is this a problem with ssh and my x-forwarding?
> > > > if so, how do you change the x-forwarding options in ssh?
> > > > if not, what is the problem and how do I fix it? :)
> > > >
> > > > thanks,
> > > > Nick.
> > > >
> > > > --
> > > > To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
> > > > with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> > >
> > > Have you installed xbase-clients?
> > >
> > > Check /etc/ssh/ssh_config and /etc/ssh/sshd_config for
> > >
> > > ForwardX11 yes
> > >
> > > and
> > >
> > > X11Forwarding yes
> > >
> > > respectively.
> > >
> > > John P Foster.
> > >
> > >
> > > --
> > > To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
> > > with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> > >
> >
> >
> > --
> > To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
> > with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> >
> >
>
>
> --
> To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
Reply to: