- kftgt release 1.6
+ kftgt release 1.7
(Kerberos v4 ticket forwarding)
Originally written by Roland Schemers and Booker Bense
Currently maintained by Russ Allbery <rra@stanford.edu>
- Copyright 1994, 1996, 1997, 1999, 2001, 2002, 2003 Board of Trustees,
- Leland Stanford Jr. University. This software is distributed under a
- BSD-style license. Please see the file LICENSE for terms of use and
- redistribution.
-
+ Copyright 1994, 1996, 1997, 1999, 2001, 2002, 2003, 2005 Board of
+ Trustees, Leland Stanford Jr. University. This software is distributed
+ under a BSD-style license. Please see the file LICENSE for terms of use
+ and redistribution.
DESCRIPTION
the AFS kaserver as the Kerberos v4 KDC and probably will not work with
other Kerberos v4 KDCs.
-
REQUIREMENTS
As a Kerberos program, kftgt requires Kerberos v4 libraries to link
As mentioned above, ticket forwarding will likely only work if your
Kerberos v4 KDC is the AFS kaserver.
-
INSTALLATION
The best way to build kftgt/kftgtd is to do something like (assuming
kftgtd is started from inetd so you need to add an entry to inetd.conf:
-kftgtd stream tcp nowait root /usr/local/sbin/kftgtd kftgtd
+ kftgtd stream tcp nowait root /usr/local/sbin/kftgtd kftgtd
And an entry in /etc/services like:
-kftgt 2109/tcp kftgtd # K4 TGT forwarding service
-
- If you change the service port you should also change it in kftgt.h and
- rebuild kftgt. It uses the value in kftgt.h in case it can't find it in
- /etc/services.
+ kftgt 2109/tcp kftgtd # K4 TGT forwarding service
+ If you change the service port you should also change it in kftgt.h and
+ rebuild kftgt. It uses the value in kftgt.h in case it can't find it in
+ /etc/services.
PORTING
kftgt should compile cleanly on most systems. I've tested it on the
following platforms:
- Digital UNIX 4.0F
- Linux (glibc 2.1 and 2.2)
- HP-UX 11.00
- AIX 4.3
- IRIX 6.5
- Solaris 2.6 and 8
+ Digital UNIX 4.0F
+ Linux (glibc 2.1, 2.2, and 2.3)
+ HP-UX 11.00
+ AIX 4.3
+ IRIX 6.5
+ Solaris 2.6 and 8
Besides the normal libraries (libkrb, libdes) you may also have to worry
about libsocket and libnsl on SysV machines, the return type for signal
also defined in kftgt.h if not found elsewhere. You might also have to
worry about the "my_" typedefs in marsh.c if you have a strange system.
-
FUTURE WORK
I didn't want to complicate things too much so I didn't worry much about