From bdeb9d9491365b08e966f1da1c536ff2a6b5d1ac Mon Sep 17 00:00:00 2001 From: Assar Westerlund Date: Sat, 28 Sep 1996 22:04:52 +0000 Subject: [PATCH] Updated man pages for kauthd, kx, and kxd. Added man pages for rxterm and rxtelnet git-svn-id: svn://svn.h5l.se/heimdal/trunk/heimdal@784 ec53bebd-3082-4978-b11e-865c3cabbd6b --- appl/kx/kx.1 | 90 ++++++++++++++++------------------------------ appl/kx/kxd.8 | 33 ++++++++++++++--- appl/kx/rxtelnet.1 | 44 +++++++++++++++++++++++ appl/kx/rxterm.1 | 44 +++++++++++++++++++++++ 4 files changed, 147 insertions(+), 64 deletions(-) create mode 100644 appl/kx/rxtelnet.1 create mode 100644 appl/kx/rxterm.1 diff --git a/appl/kx/kx.1 b/appl/kx/kx.1 index dafdc23df..c1121a718 100644 --- a/appl/kx/kx.1 +++ b/appl/kx/kx.1 @@ -1,6 +1,6 @@ .\" $Id$ .\" -.Dd August 26, 1996 +.Dd September 27, 1996 .Dt KX 1 .Os KTH-KRB .Sh NAME @@ -8,68 +8,38 @@ .Nd securely forward X conections .Sh SYNOPSIS -.Nm +.Ar kx +.Op Fl d .Ar host .Sh DESCRIPTION The .Nm -forwards a X connection from a remote client to a local screen through -an authenticated and encrypted stream. -.Sh EXAMPLES -To forward a connection from host -.Va foo -to host -.Va bar -(where the display is), you might do the following. -.Bl -enum -.It -Login to -.Va foo . -.It -Move your X-cookie from -.Va bar -to -.Va foo . -.Pp -The cookie you should move is the one used for unix-domain -connections, like: -.Bd -literal -bar.baz.com/unix:0 MIT-MAGIC-COOKIE-1 bf40ca5d710d80e400541a9ff0fb7ebc -.Ed -.Pp -On -.Va foo , -type the following -.Bd -literal -xauth add `hostname`/unix:1 . bf40ca5d710d80e400541a9ff0fb7ebc -.Ed -.It -Assuming you have added -.Nm kxd -to -.Pa inet.conf -on -.Va bar , -just start -.Nm kx -on -.Va foo : -.Bd -literal -kx bar& -.Ed -.It -Start any X applications on -.Va foo , -remember to use display 1. -.Bd -literal -xclock -display :1 -.Ed +program forwards a X connection from a remote client to a local screen +through an authenticated and encrypted stream. Options supported by +.Nm kx : +.Bl -tag -width Ds +.It Fl d +Do not fork. .El -.Sh SEE ALSO -.Xr kxd 8 -.Sh BUGS -Only works if the unix-sockets are located in -.Pa /tmp/.X11-unix . .Pp -Can only be used by one person at a time (since it only uses display -#1). +This program is used by +.Nm rxtelnet +and +.Nm rxterm +and you should not need to run it directly. +.Pp +It connects to a +.Nm kxd +on the host +.Ar host +and then will relay the traffic from the remote X clients to the local +server. When started, it prints the display and Xauthority-file to be +used on host +.Ar host +and then goes to the background, waiting for connections from the +remote +.Nm kxd. +.Sh SEE ALSO +.Xr rxtelnet 1 , +.Xr rxterm 1 , +.Xr kxd 8 diff --git a/appl/kx/kxd.8 b/appl/kx/kxd.8 index fafedb545..c3ae557e5 100644 --- a/appl/kx/kxd.8 +++ b/appl/kx/kxd.8 @@ -1,6 +1,6 @@ .\" $Id$ .\" -.Dd August 26, 1996 +.Dd September 27, 1996 .Dt KXD 8 .Os KTH-KRB .Sh NAME @@ -8,15 +8,40 @@ .Nd securely forward X conections .Sh SYNOPSIS -.Nm +.Ar kxd +.Op Fl t .Sh DESCRIPTION This is the deamon for .Nm kx . +.Pp +Options supported by +.Nm kxd : +.Bl -tag -width Ds +.It Fl t +TCP. Normally +.Nm kxd +will only listen for X connections on a UNIX socket, but some machines +(for example, Cray) have X libraries that are not able to use UNIX +sockets and thus you need to use TCP to talk to the psuedo-xserver +created by +.Nm kxd. +This option decreases the security significantly and should only be +used when it is necessary and you have considered the consequences of +doing so. +.It Fl i +Interactive. Do not expect to be started by +.Nm inetd, +but allocate and listen to the socket yourself. Handy for testing +and debugging. +.El + .Sh EXAMPLES Put the following in -.Pa inetd.conf : +.Pa /etc/inetd.conf : .Bd -literal kx stream tcp nowait root /usr/athena/libexec/kxd kxd .Ed .Sh SEE ALSO -.Xr kx 1 +.Xr kx 1 , +.Xr rxtelnet 1 , +.Xr rxterm 1 diff --git a/appl/kx/rxtelnet.1 b/appl/kx/rxtelnet.1 new file mode 100644 index 000000000..fcc705283 --- /dev/null +++ b/appl/kx/rxtelnet.1 @@ -0,0 +1,44 @@ +.\" $Id$ +.\" +.Dd September 27, 1996 +.Dt RXTELNET 1 +.Os KTH_KRB +.Sh NAME +.Nm rxtelnet +.Nd +start a telnet and forward X-connections. +.Sh SYNOPSIS +.Nm rxtelnet +.Ar host +.Sh DESCRIPTION +The +.Nm +program starts a +.Nm xterm +window with a telnet to host +.Ar host. +From this window you will also be able to run X clients that will be +able to connect securily to your X server. +.Sh EXAMPLE +To login from host +.Va foo +(where your display is) +to host +.Va bar , +you might do the following. +.Bl -enum +.It +On foo: +.Nm +.Va bar +.It +You will get a new window with a +.Nm telnet +to +.Va bar . +In this window you will be able to start X clients. +.El +.Sh SEE ALSO +.Xr rxterm 1 , +.Xr kx 1 , +.Xr kxd 8 diff --git a/appl/kx/rxterm.1 b/appl/kx/rxterm.1 new file mode 100644 index 000000000..583550d79 --- /dev/null +++ b/appl/kx/rxterm.1 @@ -0,0 +1,44 @@ +.\" $Id$ +.\" +.Dd September 27, 1996 +.Dt RXTERM 1 +.Os KTH_KRB +.Sh NAME +.Nm rxterm +.Nd +start a secure remote xterm +.Sh SYNOPSIS +.Nm rxterm +.Ar host +.Sh DESCRIPTION +The +.Nm +program starts a +.Nm xterm +window on host +.Ar host . +From this window you will also be able to run X clients that will be +able to connect securily to your X server. +.Sh EXAMPLE +To login from host +.Va foo +(where your display is) +to host +.Va bar , +you might do the following. +.Bl -enum +.It +On foo: +.Nm +.Va bar +.It +You will get a new window running an +.Nm xterm +on host +.Va bar . +In this window you will be able to start X clients. +.El +.Sh SEE ALSO +.Xr rxtelnet 1 , +.Xr kx 1 , +.Xr kxd 8