On Wed, 13 Jun 2012 11:24:23 -0700, Rick Thomas wrote:
On Jun 13, 2012, at 7:23 AM, Camaleón wrote:
Also, while searching for more information on this issue at Google I've
found many posts¹, articles and blogs² pointing to a problem with X
forwarding and ipv6 though I'm not sure this is
On Jun 13, 2012, at 11:24 AM, Rick Thomas wrote:
I will file a bug report ASAP against openssh-server.
It turns out this is bug #422327, which dates all the way back to
2007, and nothing has been done about it. The bug report even
suggested a patch (well, not exactly a patch with
On Jun 12, 2012, at 9:44 PM, Erwan David wrote:
On 13/06/12 04:12, Rick Thomas wrote:
On Jun 12, 2012, at 1:43 PM, Camaleón wrote:
... mmm, you can
compare the ... openssh versions
That got me thinking...
Looking at a third server (the same i386 Debian Squeeze machine I was
using as a
On Tue, 12 Jun 2012 19:04:26 -0700, Rick Thomas wrote:
(...)
After running full-upgrade on the servers (they had been out of action
for a couple of months, so it was a fairly large upgrade -- which makes
diagnosing the problem harder...) when I did slogin -X from any of the
clients, the
On Tue, 12 Jun 2012 19:12:42 -0700, Rick Thomas wrote:
On Jun 12, 2012, at 1:43 PM, Camaleón wrote:
... mmm, you can
compare the ... openssh versions
That got me thinking...
Looking at a third server (the same i386 Debian Squeeze machine I was
using as a client in the previous reply)
On Jun 13, 2012, at 7:23 AM, Camaleón wrote:
Also, while searching for more information on this issue at Google
I've
found many posts¹, articles and blogs² pointing to a
problem with X forwarding and ipv6 though I'm not sure this is going
to
be the case for this but it can be something to
On Jun 13, 2012, at 11:24 AM, Rick Thomas wrote:
I will file a bug report ASAP against openssh-server.
It turns out this is bug #422327, which dates all the way back to
2007, and nothing has been done about it. The bug report even
suggested a patch (well, not exactly a patch with
On Jun 9, 2012, at 3:31 AM, Camaleón wrote:
Given that you are login on your own computers you can try with -Y
flag
(untrusted X11 forwarding) and see how it goes.
Another test you can run is by creating a new user and launching
slogin -X -vvv macs xterm session from there.
Thanks for
On Tue, 12 Jun 2012 01:03:24 -0700, Rick Thomas wrote:
On Jun 9, 2012, at 3:31 AM, Camaleón wrote:
Given that you are login on your own computers you can try with -Y
flag
(untrusted X11 forwarding) and see how it goes.
Another test you can run is by creating a new user and launching
On Jun 12, 2012, at 1:43 PM, Camaleón wrote:
On Tue, 12 Jun 2012 01:03:24 -0700, Rick Thomas wrote:
On Jun 9, 2012, at 3:31 AM, Camaleón wrote:
Given that you are login on your own computers you can try with -Y
flag
(untrusted X11 forwarding) and see how it goes.
Another test you can run
On Jun 12, 2012, at 1:43 PM, Camaleón wrote:
... mmm, you can
compare the ... openssh versions
That got me thinking...
Looking at a third server (the same i386 Debian Squeeze machine I was
using as a client in the previous reply) I *can* slogin -X and get
an X session.
On both the
On 13/06/12 04:12, Rick Thomas wrote:
On Jun 12, 2012, at 1:43 PM, Camaleón wrote:
... mmm, you can
compare the ... openssh versions
That got me thinking...
Looking at a third server (the same i386 Debian Squeeze machine I was
using as a client in the previous reply) I *can* slogin
On Fri, 08 Jun 2012 11:48:15 -0700, Rick Thomas wrote:
On Jun 8, 2012, at 10:06 AM, Camaleón wrote:
On Fri, 08 Jun 2012 03:56:35 -0700, Rick Thomas wrote:
Recently, when I do slogin -X server (for one particular server, not
all of them) the resulting session can't run any X11 utilities
Recently, when I do slogin -X server (for one particular server, not
all of them) the resulting session can't run any X11 utilities (e.g.
xterm) because there is no DISPLAY variable in the environment.
It used to work. I don't know what changed for sure.
Does anybody know what can cause
On Fri, 08 Jun 2012 03:56:35 -0700, Rick Thomas wrote:
Recently, when I do slogin -X server (for one particular server, not
all of them) the resulting session can't run any X11 utilities (e.g.
xterm) because there is no DISPLAY variable in the environment.
It used to work. I don't know
On Jun 8, 2012, at 10:06 AM, Camaleón wrote:
On Fri, 08 Jun 2012 03:56:35 -0700, Rick Thomas wrote:
Recently, when I do slogin -X server (for one particular server,
not
all of them) the resulting session can't run any X11 utilities (e.g.
xterm) because there is no DISPLAY variable in the
On Jun 8, 2012, at 11:48 AM, Rick Thomas wrote:
Here's the output. I see it requesting X11 forwarding (near the
end) but I don't see anything specifically saying it was granted.
Nor do I see it being specifically refused. Fascinating...
FWIW, I tried the same 'slogin -vvv -X' to a
17 matches
Mail list logo
