1 files changed, 0 insertions, 54 deletions
diff --git a/src/gen-manpages/k5login.M b/src/gen-manpages/k5login.M
deleted file mode 100644
index dc0a84c745..0000000000
--- a/src/gen-manpages/k5login.M
+++ /dev/null
@@ -1,54 +0,0 @@
-.TH .K5LOGIN 5
-.SH NAME
-\&.k5login \- Kerberos V5 acl file for host access.
-.SH DESCRIPTION
-The
-.B .k5login
-file, which resides in a user's home directory, contains a list of the
-Kerberos principals.  Anyone with valid tickets for a principal in the
-file is allowed host access with the UID of the user in whose home
-directory the file resides.  One common use is to place a
-.B .k5login
-file in root's home directory, thereby granting system administrators
-remote root access to the host via Kerberos.
-.SH EXAMPLES
-Suppose the user "alice" had a 
-.B .k5login
-file in her home directory containing the following line:
-.sp
-.nf
-.in +1i
-bob@FUBAR.ORG
-.in -1i
-.fi
-.sp
-This would allow "bob" to use any of the Kerberos network
-applications, such as
-.IR telnet (1),
-.IR rlogin (1),
-.IR rsh (1),
-and
-.IR rcp (1),
-to access alice's account, using bob's Kerberos tickets.
-.PP
-Let us further suppose that "alice" is a system administrator.  Alice
-and the other system administrators would have their principals in
-root's
-.B .k5login
-file on each host:
-.sp
-.nf
-.in +1i
-alice@BLEEP.COM
-joeadmin/root@BLEEP.COM
-.in -1i
-.fi
-.sp
-This would allow either system administrator to log in to these hosts
-using their Kerberos tickets instead of having to type the root
-password.  Note that because "bob" retains the Kerberos tickets for
-his own principal, "bob@FUBAR.ORG", he would not have any of the
-privileges that require alice's tickets, such as root access to any of
-the site's hosts, or the ability to change alice's password.
-.SH SEE ALSO
-telnet(1), rlogin(1), rsh(1), rcp(1), ksu(1), telnetd(8), klogind(8)