.\" Things to fix:
.\"   * correct section, and operating system
.\"   * remove Op from mandatory flags
.\"   * use better macros for arguments (like .Pa for files)
.\"
.Dd July  2, 2000
.Dt KF 1
.Os Heimdal
.Sh NAME
.Nm kf
.Nd securly forward tickets
.Sh SYNOPSIS
.Nm
.Oo
.Fl p Ar port |
.Fl -port Ns = Ns Ar port
.Oc
.Oo
.Fl l Ar login |
.Fl -login Ns = Ns Ar login
.Oc
.Oo
.Fl c Ar ccache |
.Fl -ccache Ns = Ns Ar ccache
.Oc
.Op Fl F | -forwardable
.Op Fl G | -no-forwardable
.Op Fl h | -help
.Op Fl -version
.Ar host ...
.Sh DESCRIPTION
The
.Nm
program forwards tickets to a remove host through an authenticated
and encrypted stream.
Options supported are:
.Bl -tag -width indent
.It Xo
.Fl p Ar port ,
.Fl -port Ns = Ns Ar port
.Xc
port to connect to
.It Xo
.Fl l Ar login ,
.Fl -login Ns = Ns Ar login
.Xc
remote login name
.It Xo
.Fl c Ar ccache ,
.Fl -ccache Ns = Ns Ar ccache
.Xc
remote cred cache
.It Fl F , -forwardable
forward forwardable credentials
.It Fl G , -no-forwardable
do not forward forwardable credentials
.It Fl h , -help
.It Fl -version
.El
.Pp
.Nm
is useful when you do not want to enter your password on a remote host
but want to have your tickets one for example afs.
.Pp
In order for
.Nm
to work you will need to acquire your initial ticket with forwardable
flag, ie
.Nm kinit Fl -forwardable .
.Pp
.Nm telnet
is able to forward ticket by itself.
.\".Sh ENVIRONMENT
.\".Sh FILES
.\".Sh EXAMPLES
.\".Sh DIAGNOSTICS
.Sh SEE ALSO
.Xr kinit 1 ,
.Xr telnet 1 ,
.Xr kfd 8
.\".Sh STANDARDS
.\".Sh HISTORY
.\".Sh AUTHORS
.\".Sh BUGS