1 .\" Copyright (c) 2000 Kungliga Tekniska Högskolan
2 .\" (Royal Institute of Technology, Stockholm, Sweden).
3 .\" All rights reserved.
5 .\" Redistribution and use in source and binary forms, with or without
6 .\" modification, are permitted provided that the following conditions
9 .\" 1. Redistributions of source code must retain the above copyright
10 .\" notice, this list of conditions and the following disclaimer.
12 .\" 2. Redistributions in binary form must reproduce the above copyright
13 .\" notice, this list of conditions and the following disclaimer in the
14 .\" documentation and/or other materials provided with the distribution.
16 .\" 3. Neither the name of the Institute nor the names of its contributors
17 .\" may be used to endorse or promote products derived from this software
18 .\" without specific prior written permission.
20 .\" THIS SOFTWARE IS PROVIDED BY THE INSTITUTE AND CONTRIBUTORS ``AS IS'' AND
21 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
22 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
23 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE INSTITUTE OR CONTRIBUTORS BE LIABLE
24 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
25 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
26 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
27 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
28 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
29 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
39 .Nd introduction to the Kerberos system
41 Kerberos is a network authentication system. Its purpose is to
42 securely authenticate users and services in an insecure network
45 This is done with a Kerberos server acting as a trusted third party,
46 keeping a database with secret keys for all users and services
50 Each principal belongs to exactly one
52 which is the administrative domain in Kerberos. A realm usually
53 corresponds to an organisation, and the realm should normally be
54 derived from that organisation's domain name. A realm is served by one
55 or more Kerberos servers.
57 The authentication process involves exchange of
61 which together prove the principal's identity.
63 When you login to the Kerberos system, either through the normal
64 system login or with the
66 program, you acquire a
67 .Em ticket granting ticket
68 which allows you to get new tickets for other services, such as
72 without giving your password.
74 For more information on how Kerberos works, see the tutorial at
75 .Lk https://kerberos.org/software/tutorial.html
79 .Lk https://web.mit.edu/kerberos/dialogue.html .
81 For setup instructions see the Heimdal Texinfo manual.
95 The Kerberos authentication system was developed in the late 1980's as
96 part of the Athena Project at the Massachusetts Institute of
97 Technology. Versions one through three never reached outside MIT, but
98 version 4 was (and still is) quite popular, especially in the academic
99 community, but is also used in commercial products like the AFS
102 The problems with version 4 are that it has many limitations, the code
103 was not too well written (since it had been developed over a long
104 time), and it has a number of known security problems. To resolve many
105 of these issues work on version five started, and resulted in IETF RFC
106 1510 in 1993. IETF RFC 1510 was obsoleted in 2005 with IETF RFC 4120,
107 also known as Kerberos clarifications. With the arrival of IETF RFC
108 4120, the work on adding extensibility and internationalization have
109 started (Kerberos extensions), and a new RFC will hopefully appear
112 This manual page is part of the
114 Kerberos 5 distribution, which has been in development at the Royal
115 Institute of Technology in Stockholm, Sweden, since about 1997.