Lo, on Thursday, July 19, Joost Kooij did write:
The xfree86 packages have been changed to not accept tcp connections
at all by default. Check out the -nolisten option in your xserver
manual page.
I don't think this holds for potato. I'm pretty certain I never explicity
re-enabled it on
On Thu, Jul 19, 2001 at 04:04:09PM -0400, Mike wrote:
[snip]
| This might be a kinda dumb question, but does X need to be running on the
| remote machine? I've tried having X running on the remote machine, but it
| hasn't seemed to make a difference.
X must be running on the local side,
Joost Kooij wrote:
On Thu, Jul 19, 2001 at 08:27:49AM -0400, Richard
Black wrote:
> For some reason, I can no longer remote login to another terminal
and
> display stuff on mine! This started happening last week (with,
> possibly, the changes to gdm...)
>
> I have tried many different things.
Lo, on Thursday, July 19, Richard Black did write:
Joost Kooij wrote:
Generally, don't use xhost, it is not safe. Instead use xauth.
But...how do I use xauth? I have tried doing what what suggested in the man
page ie variants of
xauth extract - $DISPLAY | rsh otherhost xauth merge -
On Thu, 19 Jul 2001, Richard Black wrote:
The xfree86 packages have been changed to not accept tcp connections
at all by default. Check out the -nolisten option in your xserver
manual page.
Okay thanks!
But...how do I use xauth? I have tried doing what what suggested in the man
For some reason, I can no longer remote login to another terminal and
display stuff on mine! This started happening last week (with,
possibly, the changes to gdm...)
I have tried many different things. Typical is something like:
[local machine]
xhost +
rlogin remote
[remote machine]
export
On Thu, 19 Jul 2001, Richard Black wrote:
For some reason, I can no longer remote login to another terminal and
display stuff on mine! This started happening last week (with,
possibly, the changes to gdm...)
I have tried many different things. Typical is something like:
[local
On Thu, Jul 19, 2001 at 08:27:49AM -0400, Richard Black wrote:
For some reason, I can no longer remote login to another terminal and
display stuff on mine! This started happening last week (with,
possibly, the changes to gdm...)
I have tried many different things. Typical is something
On Thu, Jul 19, 2001 at 08:27:49AM -0400, Richard Black wrote:
| For some reason, I can no longer remote login to another terminal and
| display stuff on mine! This started happening last week (with,
| possibly, the changes to gdm...)
|
| I have tried many different things. Typical is something
Joost Kooij wrote:
On Thu, Jul 19, 2001 at 08:27:49AM -0400, Richard Black wrote:
For some reason, I can no longer remote login to another terminal and
display stuff on mine! This started happening last week (with,
possibly, the changes to gdm...)
I have tried many different things.
D-Man wrote:
I would use ssh instead of rlogin if you can. Also, enable the
ForwardX11 option in ssh. If you do this then the display will be
setup for you and it will be encrypted as well. This is also the
easiest (only?) way to display stuff back on a masq'd box.
How do you do this?
Richard Black wrote:
Joost Kooij wrote:
On Thu, Jul 19, 2001 at 08:27:49AM -0400, Richard Black wrote:
For some reason, I can no longer remote login to another terminal and
display stuff on mine! This started happening last week (with,
possibly, the changes to gdm...)
I have
On Thu, Jul 19, 2001 at 01:25:58PM -0400, Mike wrote:
| D-Man wrote:
|
| I would use ssh instead of rlogin if you can. Also, enable the
| ForwardX11 option in ssh. If you do this then the display will be
| setup for you and it will be encrypted as well. This is also the
| easiest (only?)
D-Man wrote:
On Thu, Jul 19, 2001 at 01:25:58PM -0400, Mike wrote:
| D-Man wrote:
|
| I would use ssh instead of rlogin if you can. Also, enable the
| ForwardX11 option in ssh. If you do this then the display will be
| setup for you and it will be encrypted as well. This is also the
14 matches
Mail list logo
