1K5LOGIN(5) MIT Kerberos K5LOGIN(5)
2
3
4
6 k5login - Kerberos V5 acl file for host access
7
9 The .k5login file, which resides in a user's home directory, contains a
10 list of the Kerberos principals. Anyone with valid tickets for a prin‐
11 cipal in the file is allowed host access with the UID of the user in
12 whose home directory the file resides. One common use is to place a
13 .k5login file in root's home directory, thereby granting system admin‐
14 istrators remote root access to the host via Kerberos.
15
17 Suppose the user alice had a .k5login file in her home directory con‐
18 taining just the following line:
19
20 bob@FOOBAR.ORG
21
22 This would allow bob to use Kerberos network applications, such as
23 ssh(1), to access alice's account, using bob's Kerberos tickets. In a
24 default configuration (with k5login_authoritative set to true in
25 krb5.conf(5)), this .k5login file would not let alice use those network
26 applications to access her account, since she is not listed! With no
27 .k5login file, or with k5login_authoritative set to false, a default
28 rule would permit the principal alice in the machine's default realm to
29 access the alice account.
30
31 Let us further suppose that alice is a system administrator. Alice and
32 the other system administrators would have their principals in root's
33 .k5login file on each host:
34
35 alice@BLEEP.COM
36
37 joeadmin/root@BLEEP.COM
38
39 This would allow either system administrator to log in to these hosts
40 using their Kerberos tickets instead of having to type the root pass‐
41 word. Note that because bob retains the Kerberos tickets for his own
42 principal, bob@FOOBAR.ORG, he would not have any of the privileges that
43 require alice's tickets, such as root access to any of the site's
44 hosts, or the ability to change alice's password.
45
47 kerberos(1)
48
50 MIT
51
53 1985-2020, MIT
54
55
56
57
581.18 K5LOGIN(5)