Yes, I found that. ssh is setting DISPLAY to localhost:X, but only adding an
xauth entry for `uname -n`/unix:X
hofmann:~$ ssh compileit
compileit:~$ xauth list
compileit/unix:11 MIT-MAGIC-COOKIE-1 e212a6688726a059503e0c9535289c17
compileit:~$ echo $DISPLAY
localhost:11.0
compileit:~$ xload
X
I had this problem as well, but didn't need it bad enough until I started
reading this thread and decided to look into it more.
1: make sure /etc/ssh/sshd_config has Xforwarding enabled "yes"
2: make sure you have "xbase-clients" installed, it contains the xauth program.
3: run ssh with "-X" on
On Mon, Jul 01, 2002 at 04:32:59PM -0700, Anne Carasik wrote:
| Hi Vineet,
|
| It doesn't matter--it's still does not work no matter what I do
| to my X server.
is your local routing working? i.e., can you ping localhost and
$(hostname)?
--
Michael Eyrich
> Hi all,
>
> I'm having really weird problem with X11 forwarding and two
> Debian boxes.
>
> I can login with OpenSSH and scp and everything else no
> problem.
>
> However, when I try to launch an xterm, I get either:
> can't open DISPLAY
>
> Or the display is set to server:10.0.
>
If DISPLAY=s
On 2002.07.01, Vineet Kumar <[EMAIL PROTECTED]> wrote:
> So anyway, here's a basic rundown of things to double-check:
>
> the server has "X11Forwarding yes" in its config (and that config has
> been loaded, i.e. the server has been restarted since the change).
Be specific: On the server, look at
* Vineet Kumar ([EMAIL PROTECTED]) [020701 16:51]:
> So anyway, here's a basic rundown of things to double-check:
Add to this list that "UseLogin" is set to no (its default) and
X11UseLocalhost is set to yes (its default) on the server.
> I'm about to review the thread one more time to see if you
I have tried it with woody-woody, and I got no X forwarding. Looking at
/etc/ssh/sshd_config, X11Forwarding no was there. After changing
X11Forwarding yes and restarting /etc/init.d/ssh restart, and
reconnecting, worked fine...
--
"It's a summons."
"What's a summons?"
* Anne Carasik ([EMAIL PROTECTED]) [020701 16:34]:
> Hi Vineet,
>
> It doesn't matter--it's still does not work no matter what I do
> to my X server.
>
> Anyway, I turned off xhost and X11 listening a while ago.
Right. My point was that this is a way /around/ ssh forwarding. It won't
make it any
On 2002.07.01, Anne Carasik <[EMAIL PROTECTED]> wrote:
> I need to know what DOES work, or if this is a bug.
>
> How did you get X11 working on Debian running OpenSSH 3.4p1? Did it
> just magically work for you? Did you have to set something?
Anne,
I've only been glancing at this thread but -- d
Sorry for no context, I just deleted the message before I decided to
reply...
Using ssh from debian woody to debian sid... This is the first time I
even tried to do X11 forwarding, so I didn't change anything for it...
BTW, client is i586 laptop, server is parisc(hppa) workstation. I don't
Ok... it was just a suggestion to find out the source of
the problem :)
I wasn't sure if ssh depended on xauth/host or not.
I guess it doesn't.
-David
>
> nonono! don't set your x server to listen for tcp and don't use xhost.
>
> That is the Wrong Way. The whole idea of us
Hi Vineet,
I appreciate the help, but I know that setting the DISPLAY doesn't work
either.
I need to know what DOES work, or if this is a bug.
How did you get X11 working on Debian running OpenSSH 3.4p1? Did it
just magically work for you? Did you have to set something?
-Anne
This one time,
* Ashish Gulhati ([EMAIL PROTECTED]) [020701 16:17]:
>
> > Okay, having X11 listening for TCP connections with xhost +
> > enabled didn't help.
> >
> > I'm open to other suggestions. :)
>
> Having X listening on the remote host isn't necessary for X11
> forwarding, nor is it necessary to do xhos
Hi Vineet,
It doesn't matter--it's still does not work no matter what I do
to my X server.
Anyway, I turned off xhost and X11 listening a while ago.
-Anne
This one time, Vineet Kumar wrote:
> * Anne Carasik ([EMAIL PROTECTED]) [020701 16:01]:
> > This one time, David Caplan wrote:
> > > Hi, I'm
* Anne Carasik ([EMAIL PROTECTED]) [020701 16:01]:
> This one time, David Caplan wrote:
> > Hi, I'm not exactly sure what you are trying to do, maybe this will
> > help :)
> > does it matter if you authorize the other computer with xhost?
> > or just a `xhost +` ?
>
> Nope, that didn't hel
> Okay, having X11 listening for TCP connections with xhost +
> enabled didn't help.
>
> I'm open to other suggestions. :)
Having X listening on the remote host isn't necessary for X11
forwarding, nor is it necessary to do xhost +
Just use -X and make sure the host mentioned in the DISPLAY vari
Okay, having X11 listening for TCP connections with xhost +
enabled didn't help.
I'm open to other suggestions. :)
-Anne
This one time, Anne Carasik wrote:
> Hi David,
>
> Nope, that didn't help. It may be because X11 isn't listening on
> port 6000, but I really didn't think that would affect
Hi David,
Nope, that didn't help. It may be because X11 isn't listening on
port 6000, but I really didn't think that would affect X11 forwarding.
Guess it does. I'll try and set my X11 to listen, and if that fixes
it, it goes in the FAQ :)
-Anne
This one time, David Caplan wrote:
> Hi, I'm no
Hi, I'm not exactly sure what you are trying to do, maybe this will
help :)
does it matter if you authorize the other computer with xhost?
or just a `xhost +` ?
- David
>
> So, if I force X11 with the -X (even though my ssh_config on
> the client is set to X11Forwarding yes), I get t
Clarifying myself.. sorry :)
So, if I force X11 with the -X (even though my ssh_config on
the client is set to X11Forwarding yes), I get the same as if
I don't run ssh with the -X option.
-Anne
--
.-"".__."``". Anne Carasik, System Administrator
.-.--. _...' (/) (/) ``' ga
This one time, Norbert Preining wrote:
> > It doesn't matter about the sshd_config, only the ssh_config on the
> I DEFINITELY matter what is in the sshd_config on the server. The server
> make the primary dictate on what is allowed and what is forbidden.
Well, yeah.. but you said to check the ssh_
> It doesn't matter about the sshd_config, only the ssh_config on the
I DEFINITELY matter what is in the sshd_config on the server. The server
make the primary dictate on what is allowed and what is forbidden.
Best wishes
Norbert
-
This one time, Noah L. Meyerhans wrote:
> On Mon, Jul 01, 2002 at 01:48:31PM -0700, Anne Carasik wrote:
> > So, if I force X11 with the -X (even though my ssh_config on
> > the client is set to X11Forwarding yes), I get this:
> Get what?
Uh, the output that I included.
> You don't have UseLogin s
On Mon, Jul 01, 2002 at 01:48:31PM -0700, Anne Carasik wrote:
> So, if I force X11 with the -X (even though my ssh_config on
> the client is set to X11Forwarding yes), I get this:
>
Get what?
You don't have UseLogin set in sshd_config, do you?
noah
--
This one time, Norbert Preining wrote:
> On Mon, 01 Jul 2002, Anne Carasik wrote:
> > Let me know if you have any ideas. Running the client and server in both
> > verbose and debugging modes provides me with nothing useful :(
> Did you set
> X11Forwarding yes
> in both sshd_config on server
On Mon, 01 Jul 2002, Anne Carasik wrote:
> Let me know if you have any ideas. Running the client and server in both
> verbose and debugging modes provides me with nothing useful :(
Did you set
X11Forwarding yes
in both sshd_config on server and ssh_config (.ssh/config) on client?
Best wi
On Mon, Jul 01, 2002 at 01:24:34PM -0700, Anne Carasik wrote:
> However, when I try to launch an xterm, I get either:
> can't open DISPLAY
Are you explicitly asking for X11 forwarding on the client's command
line (-X)?
> Or the display is set to server:10.0.
That is normal. That's what it shoul
27 matches
Mail list logo
