KerbNet System Administrator's Guide

Copyright © 1993, 1994, 1995, 1996, 1997 Cygnus Solutions.

KerbNet includes software and documentation developed at the Massachusetts Institute of Technology, which includes this copyright information:

Copyright © 1995, 1997 by the Massachusetts Institute of Technology.

Export of software employing encryption from the United States of America is assumed to require a specific license from the United States Government. It is the responsibility of any person or organization contemplating export to obtain such a license before exporting.

WITHIN THAT CONSTRAINT, permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of M.I.T. not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. M.I.T. makes no representations about the suitability of this software for any purpose. It is provided "as is" without express or implied warranty.


KerbNet includes software and documentation developed by OpenVision Technologies, Inc., which includes this copyright notice:

The following copyright and permission notice applies to the OpenVision Kerberos Administration system located in kadmin/create, kadmin/dbutil, kadmin/server, lib/kadm, and portions of lib/rpc:

Copyright, OpenVision Technologies, Inc., 1996, All Rights Reserved WARNING: Retrieving the OpenVision Kerberos Administration system source code, as described below, indicates your acceptance of the following terms. If you do not agree to the following terms, do not retrieve the OpenVision Kerberos administration system. You may freely use and distribute the Source Code and Object Code compiled from it, but this Source Code is provided to you "AS IS" EXCLUSIVE OF ANY WARRANTY, INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, OR ANY OTHER WARRANTY, WHETHER EXPRESS OR IMPLIED. IN NO EVENT WILL OPENVISION HAVE ANY LIABILITY FOR ANY LOST PROFITS, LOSS OF DATA OR COSTS OF PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES, OR FOR ANY SPECIAL, INDIRECT, OR CONSEQUENTIAL DAMAGES ARISING OUT OF THIS AGREEMENT, INCLUDING, WITHOUT LIMITATION, THOSE RESULTING FROM THE USE OF THE SOURCE CODE, OR THE FAILURE OF THE SOURCE CODE TO PERFORM, OR FOR ANY OTHER REASON.

OpenVision retains all rights, title, and interest in the donated Source Code. With respect to OpenVision's copyrights in the donated Source Code, OpenVision also retains rights to derivative works of the Source Code whether created by OpenVision or a third party. OpenVision Technologies, Inc. has donated this Kerberos Administration system to MIT for inclusion in the standard Kerberos 5 distribution. This donation underscores our commitment to continuing Kerberos technology development and our gratitude for the valuable work which has been performed by MIT and the Kerberos community.


KerbNet includes software and documentation developed at the University of California at Berkeley, which includes this copyright notice:

Copyright © 1983 Regents of the University of California.
All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

  1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
  2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
  3. All advertising materials mentioning features or use of this software must display the following acknowledgement:
    This product includes software developed by the University of California, Berkeley and its contributors.
  4. Neither the name of the University nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.


Permission is granted to make and distribute verbatim copies of this manual provided the copyright notices and this permission notice are preserved on all copies.

Permission is granted to copy and distribute modified versions of this manual under the conditions for verbatim copying, provided also that the entire resulting derived work is distributed under the terms of a permission notice identical to this one.

Permission is granted to copy and distribute translations of this manual into another language, under the above conditions for modified versions.

Introduction

Congratulations on your purchase of KerbNet. Cygnus Solutions believes KerbNet provides the best network security available. Please let us know if we can be of assistance in getting your installation of KerbNet set up and running.

Why Should I use Kerberos?

Since Kerberos negotiates authenticated, and optionally encrypted, communications between two points anywhere on the internet, it provides a layer of security that is not dependent on which side of a firewall either client is on. Since studies have shown that half of the computer security breaches in industry happen from inside firewalls, KerbNet from Cygnus Solutions will play a vital role in the security of your network.

KerbNet Documentation

This document is one piece of the document set for KerbNet. The documents, and their intended audiences, are:

Specific Guides for auxiliary KerbNet features that are not supported for all installations are also provided as necessary.

Using This Manual

In this manual, we will represent your prompt as "shell%". So an instruction to type the "ls" command would be represented as follows:

shell% ls

You should have install the KerbNet programs in whichever directory makes the most sense for your system. We will use /usr/cygnus/kerbnet throughout this guide to refer to the top-level directory KerbNet directory. We will therefore use /usr/cygnus/kerbnet/bin to denote the location of the KerbNet user programs.

How Kerberos Works

This chapter provides a simplified description of a general user's interaction with the Kerberos system. This interaction happens transparently--users don't need to know and probably don't care about what's going on--but Kerberos administrators might find a schematic description of the process useful. This description glosses over a lot of details; for more information, see Kerberos: An Authentication Service for Open Network Systems, a paper presented at Winter USENIX 1988, in Dallas, Texas. This paper can be retreived by FTP from athena-dist.mit.edu, in the location: /pub/ATHENA/kerberos/doc/USENIX.ps.

Network Services and Their Client Programs

In an environment that provides network services, you use client programs to request services from server programs that are somewhere on the network. Suppose you have logged in to a workstation and you want to `rlogin' to a typical UNIX host. You use the local `rlogin' client program to contact the remote machine's `rlogind' daemon.

Kerberos Services and Their Client Programs

Under Kerberos, the `klogind' daemon allows you to login to a remote machine if you can provide `klogind' a Kerberos ticket which proves your identity. In addition to the ticket, you must also posess the corresponding ticket session key. The combination of a ticket and the ticket's session key is known as a credential.

Typically, a client program automatically obtains credentials identifying the person using the client program. The credentials are obtained from a Kerberos server that resides somewhere on the network. A Kerberos server maintains a database of user, server, and password information.

The Kerberos Database

Kerberos will give you credentials only if you have an entry in the Kerberos server's Kerberos database. Your database entry includes your Kerberos principal (an identifying string, which is often just your username), and your Kerberos key, which is generated from your password. Every Kerberos user must have an entry in this database.

Kerberos Realms

Each administrative domain has its own Kerberos database, which contains information about the users and services for that particular site or domain. This administrative domain is the Kerberos realm.

Each Kerberos realm will have at least one Kerberos server, where the master Kerberos database for that site or administrative domain is stored. A Kerberos realm may also have one or more slave servers, which have read-only copies of the Kerberos database that are periodically propagated from the master server. For more details on how this is done, see the "Set Up the Slave KDCs for Database Propagation" and "Propagate the Database to Each Slave KDC" sections of the KerbNet Installation Guide.

The Ticket-Granting Ticket

The `kinit' command prompts for your password. If you enter it successfully, you will obtain a ticket-granting ticket and a ticket session key that gives you the right to use the ticket. This combination of the ticket and its associated key is known as your credentials. As illustrated below, client programs use your ticket-granting ticket credentials in order to obtain client-specific credentials as needed.

Your credentials are stored in a credentials cache, which is often just a file in /tmp. The credentials cache is also called the ticket file, especially in Kerberos V4 documentation. Note, however, that a credentials cache does not have to be stored in a file.

Network Services and the Master Database

The Kerberos database also contains entries for all network services that require Kerberos authentication. Suppose that your site has a machine, `laughter.bleep.com', that requires Kerberos authentication from anyone who wants to `rlogin' to it. The host's Kerberos realm is `BLEEP.COM'.

This service must be registered in the Kerberos database, using the proper service name, which in this case is the principal:

host/laughter.bleep.com@BLEEP.COM

The `/' character separates the Kerberos primary (in this case, `host') from the instance (in this case, `laughter.bleep.com'); the `@' character separates the realm name (in this case, `BLEEP.COM') from the rest of the principal. The primary, `host', denotes the name or type of the service that is being offered: generic host-level access to the machine. The instance, `laughter.bleep.com', names the specific machine that is offering this service. There will generally be many different machines, each offering some particular type of service, and the instance serves to give each one of these servers a different Kerberos principal.

The Keytab File

For each service, there must also be a service key known only by Kerberos and the service. On the Kerberos server, the service key is stored in the Kerberos database.

On the server host, these service keys are stored in key tables, which are files known as keytabs.(1) For example, the service keys used by secure services (such as ones that run as root on UNIX systems) are usually stored in the keytab file /etc/v5srvtab. N.B.: This service key is the equivalent of the service's password, and must be kept secure. Data which is meant to be read only by the service is encrypted using this key.

A Detailed Look at the User--Kerberos Interaction

Suppose that you walk up to a host intending to login to it, and then `rlogin' to the machine `laughter'. Here's what happens:

  1. You login to the workstation and use the `kinit' command to get a ticket-granting ticket. This command prompts you for your Kerberos password. (On UNIX systems running the KerbNet `login' program, or Windows NT systems running the KerbNet GINA, this may be done as part of the login process, without requiring the user to run a separate program.)

    1. The `kinit' command sends your request to the Kerberos master server machine. The server software looks for your principal name's entry in the Kerberos database.

    2. If this entry exists, the Kerberos server creates and returns a ticket-granting ticket and the key which allows you to use it, encrypted by your password. If `kinit' can decrypt the Kerberos reply using the password you provide, it stores this ticket in a credentials cache on your local machine for later use. The name of the credentials cache can be specified in the `KRB5_CCNAME' environment variable. If this variable is not set, the name of the file will be `/tmp/krb5cc_<uid>', where <uid> is your UNIX user-id, represented in decimal format.

  2. Now you use the `rlogin' client to access the machine `laughter'.

    host% rlogin laughter
    

    1. The `rlogin' client checks your ticket file to see if you have a ticket for the `host' service for `laughter'. You don't, so `rlogin' uses the credential cache's ticket-granting ticket to make a request to the master server's ticket-granting service.

    2. This ticket-granting service receives the request for a ticket for `host/laughter.bleep.com', and looks in the master database for an entry for `host/laughter.bleep.com'. If the entry exists, the ticket-granting service issues you a ticket for that service. That ticket is also cached in your credentials cache.

    3. The `rlogin' client now sends that ticket to the `laughter' `klogind' service program. The service program checks the ticket by using its own service key. If the ticket is valid, it now knows your identity. If you are allowed to login to `laughter' (because your username matches one in /etc/passwd, or your Kerberos principal is in the appropriate `.k5login' file), klogind will let you login.

Definitions

Following are definitions of some of the Kerberos terminology.

authentication
the process of proving the identity of one entity on the internet (a user or service) to another entity.

client
an entity that can obtain a ticket. This entity is usually either a user or a host.

credentials cache
the location where KerbNet stores tickets. The credentials cache is frequently a file, but it may just be a place in memory.

expiration
tickets cease to be valid when they expire. The amount of time tickets have before expiration is chosen by the user when obtaining the tickets; the maximum allowable lifetime for different kinds of tickets is preset by the System Administrator.

forwardable tickets
Kerberos tickets that can be forwarded (copied) to a remote machine; the copies can be used on the remote machine, eliminating the need to obtain new tickets on that machine.

host
a computer that can be accessed over a network. A remote host is one that is accessed electronically through another host, rather than directly.

Kerberos
in Greek mythology, the three-headed dog that guards the entrance to the underworld. In the computing world, Kerberos is a network security package that was developed at MIT.

KDC
Key Distribution Center. A machine that issues Kerberos tickets.

keytab
a key table file containing one or more keys. A host or service uses a keytab file in much the same way as a user uses his/her password.

principal
a string that names a specific entity to which a set of credentials may be assigned. It generally has three parts:

primary
the first part of a Kerberos principal. The primary identifies the individual user (for a user principal) or the type of service (for a service principal). A user's primary is his/her username.

instance
the second part of a Kerberos principal. It gives information that qualifies the primary. If the principal represents a user, the instance is usually null (blank), but can also be used to describe the intended use of the corresponding credentials. If the principal represents a host, the instance is the fully qualified hostname.

realm
the logical network served by a single Kerberos database and a set of Key Distribution Centers. By convention, realm names are generally all uppercase letters, to differentiate the realm from the internet domain.

The typical format of a typical Kerberos principal is primary/instance@REALM.

  • service any program or computer you access over a network. Examples of services include "host" (a host, e.g., when you use telnet and rsh), "ftp" (FTP), "krbtgt" (authentication; cf. ticket-granting ticket), and "pop" (email).

  • single-sign-on system a security system that asks for initial confirmation of the user's identity, but then does all further authenticaton automatically. With a single-sign-on system, a user only needs to type his or her password once, at the beginning of the session.

  • telnet port the "address" that the telnet applications connects to on a computer.

  • ticket a temporary set of electronic credentials that verifies the identity of its to a particular service.

  • TGT Ticket-Granting Ticket. A special Kerberos ticket that permits its owner to obtain additional Kerberos tickets within the same Kerberos realm. A TGT is obtained during the initial authentication process.
  • Administration of the Kerberos Database

    Your Kerberos database contains all of your realm's Kerberos principals, their passwords, and other administrative information about each principal. As System Administrator, you have the power to change information in the database. Tasks that you may want to perform include:

    * adding and deleting principals to the Kerberos database

    * modfiying the restrictions governing passwords

    * granting administrative privileges to specific principals

    * changing the default lifetime of tickets

    * manipulating the database as a whole (e.g. backing it up).

    Most of these tasks are done by interacting with one of the administrative programs, particularly when you are dealing with a few specific principles. These tasks are described in the following section. However, some of the global defaults for the database, such as the default lifetime of tickets, are controled in the kdc.conf file as described in see section kdc.conf.

    You can manipulate information in the Kerberos database using either the Admin GUI (window-style user interface) or by typing commands at the command line (DOS or UNIX prompt).

    This chapter describes the general tasks you can perform; the next two chapters give specific instructions for performing these tasks using each of the two interface options. Chapter 6 explains how to manipulate the database as a whole.

    Principals

    Entities that can recieve Kerberos tickets are represented by Kerberos principals (see section Definitions). Each entry in the Kerberos database contains a Kerberos principal and the attributes and policies associated with that principal.

    Adding and Modifying Principals

    You can add a principal to the Kerberos database, using either the Admin GUI or the command line. When you add a principal, you must give it a temporary password; if the principal corresponds to a user, you should tell the user to change the password right away. You can set an option that forces the user to change the password the first time he or she logs in using the principal.

    If you need cross-realm authentication, you must add principals for the other realm's TGT to each realm. For example, if you need to do cross-realm authentication between the realms BLEEP.COM and FUBAR.ORG, you would need to add the principals `krbtgt/FUBAR.ORG@BLEEP.COM' and `krbtgt/BLEEP.COM@FUBAR.ORG' to both databases. You need to be sure the passwords and the key version numbers (kvno) are the same in both databases. This may require explicitly setting the kvno with the `-kvno' option (see section Adding or Modifying Principals).

    You can also modify the administrative information of principals already in the database.

    Deleting Principals

    You can delete principals from the Kerberos database, using either the Admin GUI or the command line.

    When you delete a principal from the Kerberos database, be sure to remove that principal from all files that grant access privileges (see section Administrative Privileges). Otherwise, if the principal is later reassigned, it will still have the privileges granted in those files, whether the new owner of the principal ought to have them or not.

    For example, if a user with the username `jennifer' has full administrative privileges for the BLEEP.COM domain, the `kadm5.acl' file would have the entry:

    
    jennifer@BLEEP.COM admcil 
    
    

    If Jennifer leaves and a new employee with the first name Jennifer is given the username `jennifer', the new employee has full administrative privileges for BLEEP.COM, because the principal `jennifer' is still listed in `kadm5.acl' with those privileges.

    Rather than deleting a principal that is no longer is use, it may be easier to simply "deactivate" the principal by assigning it a random password. Then no new user can be assigned the principal, and there is no danger of accidentally granting a new user inappropriate access privileges. You can also deactivate a principal by taking away its ability to receive tickets (see section Deactivating a Principal,or section Attributes).

    Changing Attributes of Principals

    Principals have associated attributes, which are rules governing what kind of tickets a principal is allowed to obtain and under what circumstances it can obtain tickets. Each attribute is controlled by an on/off flag in the database entry for a principal; when the attribute appears in the entry, the flag is "on". By default, principals have no attribute flags turned on. You can set attributes for a principal using either the Admin GUI or the command line.

    Principals may have the following attribute flags associated with them:

    DISALLOW POSTDATED
    prohibits the principal from obtaining postdated tickets. Postdated tickets can be made valid by the KDC at a future time without the secret key used to create them. There is support for post-dated tickets in kinit.

    Disallow Forwardable
    prohibits the principal from obtaining forwardable tickets. When KerbNet forwards a ticket to a remote host, it makes a copy of the ticket in that host's credentials cache. The ticket's owner can then use the credentials on the remote machine, without having to reauthenticate. KerbNet can only forward tickets designated as forwardable.

    Disallow Renewable
    prohibits the principal from obtaining renewable tickets. A renewable ticket has a short lifespan, but the ticket's owner can add additional time to the ticket's lifespan without having to reauthenticate. Only tickets designated as renewable may be renewed.

    Disallow Proxiable
    prohibits the principal from obtaining proxiable tickets. Support for proxiable tickets is not available at this time.

    Disallow Duplicate SKEY
    disables user-to-user authentication for this principal by prohibiting the principal from obtaining a session key for another user. This type of authentication is not currently used in KerbNet applications.

    Requires Preauth
    requires the principal to preauthenticate before being allowed to kinit. Preauthentication is a process in which the Kerberos server sends a request for electronic verification of the user's identity before sending the encrypted TGT.

    Requires Hardware Auth
    requires the principal to preauthenticate using a hardware device before being allowed to kinit. Hardware preauthentication is similar to preauthentication, except that the verification information is generated by a separate hardware device kept by the principal's owner.

    Disallow SVR
    prohibits the issuance of service tickets for the principal.

    Disallow TGT Based
    specifies that a Ticket-Granting Service (TGS) request for a service ticket for the principal is not permitted. You will probably never need to use this option.

    Disallow ALL Tickets
    prohibits the principal from obtaining any tickets.

    Requires Password Change
    forces a password change the next time the principal requests a TGT.

    Password Changing Service
    marks this principal as a password change service. You will probably never need to use this option.

    Policies

    A policy is a set of rules governing passwords. Policies dictate minimum and maximum password lifetimes, minimum number of characters and character classes a password must contain, and the number of previous passwords kept in the database for a given principal.

    Policies are stored in a database, `principal.kadm', separate from the Kerberos database. You can create new policies, modify existing policies, and delete policies using either the Admin GUI or the command line.

    You can assign a policy to a principal by modifying the administrative information about that principal. You can assign each policy to as many principals as you want, but a single principal cannot have more than one policy. By default, principals have no policy.

    Make sure that you cancel a policy from all principals before deleting the policy from the database. KerbNet will not delete a policy if it currently applies to any principal.

    When you change a policy, the changes affect the principals that have that policy the next time the system needs to check the relevant attributes. So, for example, if you change a policy so that the maximum password lifetime is less than the amount of time that has passed since a principle with that policy changed its password, the will be forced to change their password the next time that principal tries to obtain a TGT. On the other hand, if a principal's password has only one class of characters in it, and you change the policy that governs that principal to require two character classes, the change will not affect the user until the user changes the password, at which point the system will enforce the new restrictions.

    Administrative Privileges

    Administrative privileges for the Kerberos database are stored in the file kadm5.acl. Each line of the file contains a principal, the privileges that principal has, and optionally the target to which those permissions apply. The privileges are represented by single letters; UPPER-CASE letters represent negative permissions. The permissions are:

    a
    allows the addition of principals or policies in the database.
    A
    disallows the addition of principals or policies in the database.
    d
    allows the deletion of principals or policies in the database.
    D
    disallows the deletion of principals or policies in the database.
    m
    allows the modification of principals or policies in the database.
    M
    disallows the modification of principals or policies in the database.
    c
    allows the changing of passwords for principals in the database.
    C
    disallows the changing of passwords for principals in the database.
    i
    allows inquiries to the database.
    I
    disallows inquiries to the database.
    l
    allows the listing of principals or policies in the database.
    L
    disallows the listing of principals or policies in the database.
    *
    All privileges (admcil).
    x
    All privileges (admcil); identical to "*".

    Principals in this file can include the * wildcard. Here is an example of a kadm5.acl file. Note that order is important; permissions are determined by the first matching entry.

    */admin@BLEEP.COM  *
    jschmoe/null@BLEEP.COM  ADMCIL
    jschmoe/*@BLEEP.COM  il
    jennifer/root@BLEEP.COM  cil  */root@BLEEP.COM
    */*@BLEEP.COM  i
    

    In the above file, any principal with an admin instance has all administrative privileges. The user jschmoe has all permissions with his admin instance, jschmoe/admin@BLEEP.COM (matches the first line). He has no permissions at all with his null instance, jschmoe/null@BLEEP.COM (matches the second line). He has inquire and list permissions with any other instance (matches the third line). When jennifer is using her root instance, jennifer/root@BLEEP.COM, she has change password, inquire, and list privileges for any other principal that has the instance root. Finally, any principal in the realm BLEEP.COM (except for jschmoe/null@BLEEP.COM, as mentioned above) has inquire privileges.

    To change the privileges associated with a particular principal, modify the kadm5.acl file directly.

    Other Information

    Date Format

    Both the command line and the GUI often require input in the form of dates. A date can appear in a wide variety of formats, such as:

    1 month
    2 hours
    400000 seconds
    next year
    this Monday
    next Monday
    yesterday
    tomorrow
    now
    second Monday
    a fortnight
    3/31/98 10:00:07 PST
    January 23, 1997 10:05pm
    22:00 GMT
    

    All of these are case-insensitive. The following is a list of all of the allowable keywords.

    Months
    january, jan, february, feb, march, mar, april, apr, may, june, jun, july, jul, august, aug, september, sept, sep, october, oct, november, nov, december, dec

    Days
    sunday, sun, monday, mon, tuesday, tues, tue, wednesday, wednes, wed, thursday, thurs, thur, thu, friday, fri, saturday, sat

    Units
    year, month, fortnight, week, day, hour, minute, min, second, sec

    Relative
    tomorrow, yesterday, today, now, last, this, next, first, third, fourth, fifth, sixth, seventh, eighth, ninth, tenth, eleventh, twelfth, ago

    Time Zones
    kadmin recognizes abbreviations for most of the world's time zones. A complete listing appears in section kadmin Time Zones.

    12-hour Time Delimiters
    am, pm

    Administration Using the Admin GUI

    The Admin GUI (Graphical User Interface) is an interface that lets you manipulate information in the Kerberos database using windows and menus. The GUI is available on both UNIX and NT systems.

    This chapter describes how to administer the Kerberos database using the Admin GUI.

    The Principal Information Window

    Starting Up

    To start the Admin GUI:

    1. Type the command tkadmin at the command line (UNIX or DOS prompt).

    The `tkadmin' command takes the following options:

    -r REALM or --realm REALM
    administer the specified realm

    If you do not specify a realm, `tkadmin' will use the local realm by default.

    -p PRINCIPAL or --principal PRINCIPAL
    log in as the specified principal

    If you do not specify a principal, `tkadmin' will use `<userid>/admin', where <userid> is the userid you are currently logged in as.

    -w PASSWORD or --password PASSWORD
    log in using the specified password

    Because this option requires you to type your password openly, it is insecure; someone could look at your screen or use your machine later to retrieve your password. You should avoid using this option.

    -d or --debug
    send debugging information to stdout.

    -h or --help
    lists the options to tkadmin

    If you do not use the password option, the Password entry dialog opens and prompts you for your password.

    1. Type your password and hit Return.

    The Principal list window opens.

    The Principal List window displays all the principals in the Kerberos database.

    Listing Selected Principals

    By default, the principal list shows all the principals in the database. However, you can view a subset of the principals by selecting an appropriate filter. A filter is a string of characters that all the principals you want to view have in common; the Principal List window displays all the principals in the database that contain that string.

    The wildcard `*' stands for any number of characters. Thus, the filter `*/admin' causes the principal list to display any principal with the instance `admin'; the filter `host/*' matches any principal with the primary `host'. The filter `host*' would also retrieve all principals with the primary `host', as well as principals such as `host@BLEEP.COM' `hostess/admin@BLEEP.COM'. The filter `host' would retrieve only the principal `host@BLEEP.COM' (the exact match to the filter string).

    The `*' filter lists all the principals in the database.

    To change the current filter:

    1. Click on the Filter button and select a filter from the drop-down list, or type the desired filter into the text box beside the Filter button.

    The Principal List now displays only those principals that match the specified filter string.

    The File Menu

    Refreshing Displayed Information

    The Admin GUI lets you view and edit the contents of the Kerberos database and the policy database. However, although the information it displays changes to reflect changes you make, changes made by other people while you have the GUI open do not appear unless you tell the GUI to update its version of the databases.

    To update the information in the GUI:

    1. Select Refresh from the File menu.

    The GUI updates its database displays.

    Exiting the Admin GUI

    1. Select Quit from the File menu to close the Principal List window.

    The Principal Menu

    The commands on the Principals menu allow you to manipulate entries in the Kerberos database.

    Adding Principals

    To add a new principal to the database:

    1. Choose Add New from the Principals menu.

    The Principal Information dialog appears.

    1. In the Principal text box, enter the principal.

      If you do not specify a realm for the principal, it will have the realm you specified when you ran the `tkadmin' command, or the default realm for the domain you are in (if you did not specify a realm when you ran `tkadmin').

    2. In the Principal Expires text box, enter the date and time when the principal will expire.

    3. In the Password Expires text box, enter the date and time when the principal's password will expire.

    4. In the Max Ticket Lifetime text box, enter the maximum amount of time for which the principal's tickets can be valid.

    5. In the Max Renewable Life text box, enter the time span during which the principal's tickets (if renewable) may be renewed.

    6. The Password Policy text box shows the policy governing the principal's password. To change the policy, click in the text box and select a policy from the drop-down list. See section Modifying a Policy, for information about adding policies to the list and modifying existing policies.

    You can edit these values as much as you like. Clicking the Revert button beside a text box causes the current saved value to appear in that text box, replacing whatever value you have typed. Clicking the Revert All button will revert the text in all text boxes to the current saved values.

    Although you may enter dates and durations in various different formats (see section Date Format), they will appear in standard formats in the text boxes (for example, "next monday" might appear as "Mon Mar 10 00:00:00 EST 1997.").

    If you have entered an inappropriate value in one of the textboxes (for example, a date with an invalid format), that text appears red when you move the cursor out of that text box or try to commit your changes. After you have entered an appropriate value, the text becomes black again the next time you move the cursor to another text box, commit your changes, or use a Revert button.

    1. Set the attribute flags (see section Changing Attributes of Principals) for the principal by selecting and deselecting the checkboxes at the bottom of the Principal Information dialog.

      Disallow TGT Based
      Checking this checkbox sets the `Disallow TGT Based' flag on the principal in the database, specifying that a Ticket-Granting Service (TGS) request for a service ticket for this principal is not permitted.

      Disallow Forwardable
      Checking this checkbox sets the `Disallow Forwardable' flag on the principal in the database, prohibiting the principal from obtaining forwardable tickets.

      Disallow Postdated
      Checking this checkbox sets the `Disallow Postdated' flag on the principal in the database, prohibiting the principal from obtaining postdated tickets.

      Disallow Duplicate SKey
      Checking this checkbox sets the `Disallow Duplicate SKey' flag on the principal in the database, prohibiting the principal from obtaining a session key for another user.

      Disallow Proxiable
      Checking this checkbox sets the `Disallow Proxiable' flag. on the principal in the database, prohibiting the principal from obtaining proxiable tickets.

      Disallow Renewable
      Checking this checkbox sets the `Disallow Renewable' flag on the principal in the database, prohibiting this principal from obtaining renewable tickets.

      Requires Hardware Auth
      Checking this checkbox sets the `Requires Hardware Auth' flag on the principal in the database, requiring the principal to preauthenticate using a hardware device before being allowed to kinit.

      Requires Preauth
      Checking this checkbox sets the `Requires Preauth' flag on the principal in the database, requiring the principal to preauthenticate before being allowed to kinit.

      Disallow All Tickets
      Checking this checkbox sets the `Disallow All Tickets' flag on the principal in the database, forbiding the issuance of any tickets for this principal.

      Password Changing Service
      Checking this checkbox sets the `Password Changing Service' flag on the principal in the database, marking this principal as a password change service.

      Disallow SVR
      Checking this checkbox sets the `Disallow SVR' flag on the principal in the database, prohibiting the the principal from obtaining service tickets.

      Requires Password Change
      Checking this checkbox the `Requires Password Change' flag on the principal in the database, forcing a password change the next time the principal requests a TGT. You can also set this flag as part of the process of changing a principal's password (see section Changing a Password).

    2. Click the Set Password button

    The Password Entry dialog opens.

    1. Type a password for the new principal twice (once in each of the text boxes).

    2. Select the Force checkbox to force the user to change the password the first time he or she logs in using this principal.

    3. Click the OK button to close the Password Entry dialog.

    4. Click the Commit Add button to add the principal to the database, or click the Cancel button to close the Principal Information dialog without creating a new principal.

    You cannot create a new principal without assigning it a name and a password. If you click Commit Add without first setting the password, the Password Entry dialog opens, prompting you to enter a password. When you click OK in the Password Entry dialog, the Principal Information closes as well, and the new principal is entered in the database.

    Deleting Principals

    To delete one or more principals from the database:

    1. Select the principals you wish to delete by clicking on them in the Principal List (for multiple principals, hold down Shift and click).

    2. Choose Delete from the Principals menu.

    A dialog box will appear, asking you to confirm the deletion. If you click Yes, the principal is deleted from the database.

    Displaying and Modifying Information About a Principal

    To display further information about a principal, select Edit from the Principal menu, or double-click on the principal in the Principal List. The Principal Information dialog opens.

    The Principal Information dialog displays administrative information about the selected principal. You can look at a different principal by double-clicking on the new principal in the Principal List window; information on that principal will appear in the open Principal Information window.

    You can modify the information in text boxes whose titles have blue backgrounds by typing new values into the appropriate text boxes. You can also modify the attribute flags on the principal by selecting and deselecting the checkboxes at the bottom of the Principal Information dialog. See section Adding Principals, for an explanation of these fields.

    Clicking the Revert button beside a text box causes the current saved value to appear in that text box, replacing whatever value you have typed. Clicking the Revert All button will revert the text in all text boxes to the current saved values.

    Click the Commit Changes button to add the new information to the database, or click the Cancel button to close the Principal Information dialog without changing the principal's information.

    The information in the fields whose titles have black backgrounds is historical information about the principal; you cannot modify these values. Note that the Principal field is unmodifiable. See section Renaming a Principal, for information about renaming a principal.

    * Last Password Change displays the time when the principal's password was last changed.

    * Last Modification displays the time when the principal's administrative information was last modified.

    * Last Modification By displays the principal responsible for the last modification of this principal's administrative information.

    The following fields relate to preauthentication features that have not been fully implemented yet.

    * Last Successful Auth

    * Last Failed Auth

    * Failed Password Attempts

    * Key Version Number The Key Version Number keeps track of how many times the principal's key has been changed. See section Keys and Key Version Numbers, for more information about Key Version Numbers.

    Renaming a Principal

    To rename a principal:

    1. Select the principal in the Principal List window.

    2. Select Rename from the Principal menu.

    The Rename dialog opens.

    1. Enter the new name in the New Name text box and click Commit Rename to commit the change to the database.

    The Password Entry dialog will open, as if you had created a new principal.

    1. Assign a new password to the renamed principal.

    Copying a Principal

    You can copy a principal, creating a second principal with all attributes identical to those of the first, except for the principal name.

    To copy a principal:

    1. In the principal list, select the principal you want to copy.

    2. Select Copy from the Principal menu.

    The Principal Information dialog opens. The New Name text box is blank; all the other text boxes display the copied attribute values.

    1. Enter the new principal in the New Name text box.

    2. Click the Set Password button. Assign a password to the new principal, as you would for a new principal (see section Adding Principals).

    3. Click Commit Copy to enter the new principal into the Kerberos database.

    4. Click Cancel to close the Principal Information window.

    Changing a Password

    To change a principal's password:

    1. Select that principal in the Principal List and choose Change Password from the Principal menu. Alternatively, select Edit from the Principal menu and clicking the Change Password button in the Principal Information window.

    The Password Entry dialog appears.

    1. Type the new password in each of the two text boxes.

    2. Select the Force checkbox if you want to force the user to change the password the next time he or she logs in.

    3. Click OK to enter the new password in the database, or click Cancel to close the Password Entry dialog without changing the password.

    A dialog appears, telling you that the password has been changed or warning you if the password could not be changed (e.g. the password you chose was already in the principal's password history).

    Deactivating a Principal

    The Deactivate command sets the `Disallow All Tickets' flag on a principal, thereby making it impossible for the principal to obtain tickets. Note that if you later reactivate the principal, it will still have any permissions it had before, since it has not been removed from any permissions lists (see section Adding and Modifying Principals).

    To deactivate a principal:

    1. Select one or more principals from the Principal List window.

    2. Select Deactivate from the Principal menu.

    A dialog appears, confirming the deactivation.

    1. Click OK

    The principals are deactivated. Note that they still appear in the principals list, and you can still view and change their information.

    Reactivating a Principal

    To reactivate a principal:

    1. Select one or more principals in the Principal List window.

    2. Select Reactivate from the Principal menu.

    A dialog appears, confirming the reactivation.

    1. Click OK.

    The principals are reactivated.

    The Policy Menu

    The Policy List Dialog

    Selecting Show List from the Policy menu opens the Policy List dialog. The Policy List lists all the policies in the database.

    Selecting Close from the File menu in the Policy List dialog closes the Policy List dialog.

    Creating a Policy

    To create a new password policy:

    1. Select Add New from the Policy menu in the Policy List dialog.

    The Policy Information window opens.

    1. Enter the policy name in the Policy text box.

    2. Enter the minimum password lifetime in the Min Lifetime text box.

    3. Enter the maximum password lifetime in the Max Lifetime text box.

    4. Enter the minimum number of characters a password must contain in the Min Password Length text box.

    5. Enter the number of previous passwords to be stored for a principal in the Old Keys text box.

    6. Enter the minimum number of character classes a password must use in the Min Character Classes text box.

    7. Click the Commit Changes button to add the new policy to the policy database.

    8. Click the Cancel button to close the Policy Information window. Any changes you have made since you last clicked Commit Changes will be lost.

    Clicking the Revert button beside a text box causes the current saved value to appear in that text box, replacing whatever value you have typed. Clicking the Revert All button will revert the text in all text boxes to the current saved values.

    Deleting a Policy

    To delete an existing policy:

    1. Choose Show List from the Policy menu, if the Policy List is not already open.

    2. In the Policy List window, select the policy you want to delete.

    3. Choose Delete from the Policy menu in the Policy List dialog. A dialog will appear asking you to confirm the deletion. If you click Yes, the policy is deleted from the policy database.

    You must remove the policy from all principals before attempting to delete it. If a policy is in use, an attempt to delete it will fail. The Principals Using Policy field in the Policy Information window tells you how many principals currently have the policy.

    Modifying a Policy

    To modify an existing policy:

    1. Choose Show List from the Policy menu, if the Policy List is not already open.

    2. Double-click the policy in the Policy List or choose Edit from the Policy menu.

    The Policy Information window appears.

    1. Modify the fields (see section Creating a Policy, for an explanation of these fields). Clicking the Revert button beside a text box causes the current saved value to appear in that text box, replacing whatever value you have typed. Clicking the Revert All button will revert the text in all text boxes to the current saved values.

    2. Click the Commit Changes button to save your changes to the policy. Click the Cancel button to close the Policy Information window (any changes you have not committed when you click Cancel will be lost).

    Copying a Policy

    You can copy a policy, creating a second policy with all attributes identical to those of the first, except for the policy name.

    To copy a policy:

    1. In the principal list, select the principal you want to copy.

    2. Select Copy from the Policy menu in the Policy List dialog.

    The Policy Information dialog opens. The `New Name' text box is blank; all the other text boxes display the copied attribute values.

    1. Enter the new policy name in the `New Name' text box.

    2. Click Commit Copy to enter the new policy into the policy database.

    Administration Using the Command Line Program

    This chapter describes how to manipulate information in the Kerberos database using the UNIX or Windows NT command line. The commands are the same for both operating systems. The one difference is that when specifying pathnames for kadmin or kadmin.local on Windows NT systems the path must be proceeded by `WRFILE:' for writable files such as keytabs and `FILE:' for read only files.

    The kadmin program allows you to make changes to the entries in the database. The users can use the kpasswd program to change their own passwords. The kdb5_util program allows you to manipulate the Kerberos database as a whole (see section Manipulating the Kerberos Database).

    The kadmin program has its own command-line interface, to which you type the database administrating commands. Kadmin provides for the maintenance of Kerberos principals, KADM5 policies, and service key tables (keytabs). It exists as both a Kerberos client, kadmin, using Kerberos authentication and an RPC, to operate securely from anywhere on the network, and as a local client, kadmin.local, intended to run directly on the KDC without Kerberos authentication. Other than the fact that the remote client uses Kerberos to authenticate the person using it, the functionalities of the two versions are identical. The local version is necessary to enable you to set up enough of the database to be able to use the remote version. Kadmin replaces the now obsolete kdb5_edit (except for database dump and load, which are provided by kdb5_util).

    The remote version of kadmin authenticates to the KADM5 server using the service principal kadmin/admin. If the credentials cache contains a ticket for the kadmin/admin principal, and the `-c credentials_cache' option is specified, that ticket is used to authenticate to KADM5. Assuming you don't already have a kadmin/admin ticket, you will need to use the `-p' or `-k' option to specify the client Kerberos principal name that will be used to authenticate.

    Kadmin Options

    You can invoke kadmin with any of the following options:

    -r REALM
    Use REALM as the default Kerberos realm for the database.

    -p principal
    Use the Kerberos principal principal to authenticate to Kerberos. If this option is not given, kadmin will append admin to either the primary principal name, the environment variable USER, or to the username obtained from getpwuid, in order of preference.

    -k keytab
    Use the keytab keytab to decrypt the KDC response instead of prompting for a password on the TTY. In this case, the principal will be `host/hostname'.

    -c credentials cache
    Use credentials_cache as the credentials cache. The credentials cache should contain a service ticket for the kadmin/admin service, which can be acquired with the kinit program. If this option is not specified, kadmin requests a new service ticket from the KDC, and stores it in its own temporary ccache.

    -w password
    Use password as the password instead of prompting for one on the TTY. Note: placing the password for a Kerberos principal with administration access into a shell script can be dangerous if unauthorized users gain read access to the script.

    -q query
    Pass query directly to kadmin. This is useful for writing scripts that pass specific queries to kadmin.

    Principals

    Retrieving Information About a Principal

    Attributes

    To retrieve a listing of the attributes and/or policies associated with a principal, use the kadmin get_principal command, which requires the "inquire" administrative privilege. The syntax is:

    get_principal principal
    

    The get_principal command has the alias getprinc.

    For example, suppose you wanted to view the attributes of the principals jennifer/root@BLEEP.COM and systest@BLEEP.COM. You would type:

    shell% kadmin
    kadmin: getprinc jennifer/root
    Principal: jennifer/root@BLEEP.COM
    Key version: 3
    Maximum life: 1 day 00:00:00
    Maximum renewable life: 7 days 00:00:00
    Master key version: 1
    Expires: Mon Jan 18 22:14:07 EDT 2038
    Password expires: Mon Sep 19 14:40:00 EDT 1996
    Password last changed: Mon Jan 31 02:06:40 EDT 1996
    Last modified: by jschmoe/admin@BLEEP.COM
    	on Wed Jul 13 18:27:08 EDT 1996
    Attributes: DISALLOW_FORWARDABLE, DISALLOW_PROXIABLE,
    	REQUIRES_HW_AUTH
    Salt type: DEFAULT
    kadmin:
    

    The get_principal command has a -terse option, which lists the fields as a quoted, tab-separated string. For example:

    kadmin: getprinc -terse systest
    systest@BLEEP.COM	3	86400	604800	1
    785926535	753241234	785900000
    jennifer/admin@BLEEP.COM	786100034	0
    0
    kadmin:
    

    Retrieving a List of Principals

    To generate a listing of principals, use the kadmin list_principals command, which requires the "list" privilege. The syntax is:

    list_principals [expression]
    

    where expression is a shell-style glob expression that can contain the characters `*', `?', `[', and `]'. All policy names matching the expression are displayed. The list_principals command has the alias listprincs. For example:

    kadmin: listprincs test*
    test3@bleep.com
    test2@bleep.com
    test1@bleep.com
    testuser@bleep.com
    kadmin:
    

    If no expression is provided, all principals are printed.

    Adding or Modifying Principals

    To add a principal to the database, use the kadmin add_principal command, which requires the "add" administrative privilege. The syntax is:

    kadmin: add_principal [options] principal
    

    To modify attributes of a principal, use the kadmin modify_principal command, which requires the "modify" administrative privilege. The syntax is:

    kadmin: modify_principal [options] principal
    

    add_principal has the aliases addprinc and ank(2). modify_principal has the alias modprinc.

    The add_principal and modify_principal commands take the following switches:

    -salt salttype
    Uses the specified salt for generating the key. The valid salt types are:

    -clearpolicy
    removes the current policy from a principal (modify_principal only).

    -expire date
    Sets the expiration date of the principal to date.

    -pwexpire date
    Sets the expiration date of the password to date.

    -maxlife maxlife
    Sets the maximum ticket life of the principal to maxlife.

    -kvno number
    Explicity sets the key version number to number. Cygnus Solutions does not recommend doing this unless there is a specific reason.

    -policy policy
    Sets the policy used by this principal. (See section Policies.) If no policy is supplied, the principal will have no policy.

    {-|+}allow_postdated
    The "-allow_postdated" option sets the `Disallow Postdated' flag on the principal in the database, prohibiting the principal from obtaining postdated tickets. "+allow_postdated" clears this flag.

    {-|+}allow_forwardable
    The "-allow_forwardable" option sets the `Disallow Forwardable' flag on the principal in the database, prohibiting the principal from obtaining forwardable tickets. "+allow_forwardable" clears this flag.

    {-|+}allow_renewable
    The "-allow_renewable" option sets the `Disallow Renewable' flag on the principal in the database, prohibiting this principal from obtaining renewable tickets. "+allow_renewable" clears this flag.

    {-|+}allow_proxiable
    The "-allow_proxiable" option sets the `Disallow Proxiable' flag. on the principal in the database, prohibiting the principal from obtaining proxiable tickets. "+allow_proxiable" clears this flag.

    {-|+}allow_dup_skey
    The "-allow_dup_skey" option sets the `Disallow Duplicate SKey' flag on the principal in the database, prohibiting the principal from obtaining a session key for another user. "+allow_dup_skey" clears this flag.

    {-|+}requires_preauth
    The "+requires_preauth" option sets the `Requires Preauth' flag on the principal in the database, requiring the principal to preauthenticate before being allowed to kinit. "-requires_preauth" clears this flag.

    {-|+}requires_hwauth
    The "+requires_hwauth" option sets the `Requires Hardware Auth' flag on the principal in the database, requiring the principal to preauthenticate using a hardware device before being allowed to kinit. "-requires_hwauth" clears this flag.

    {-|+}allow_svr
    The "-allow_svr" option sets the `Disallow SVR' flag on the principal in the database, prohibiting the the principal from obtaining service tickets. "+allow_svr" clears this flag.

    {-|+}allow_tgs_req
    The "-allow_tgs_req" option sets the `Disallow TGT Based' flag on the principal in the database, specifying that a Ticket-Granting Service (TGS) request for a service ticket for this principal is not permitted. "+allow_tgs_req" clears this flag. The default is "+allow_tgs_req".

    {-|+}allow_tix
    The "-allow_tix" option sets the `Disallow All Tickets' flag on the principal in the database, forbiding the issuance of any tickets for this principal. "+allow_tix" clears this flag. The default is "+allow_tix".

    {-|+}needchange
    The "+needchange" option sets the `Requires Password Change' flag on the principal in the database, forcing a password change the next time the principal obtains a TGT; "-needchange" clears it. The default is "-needchange".

    {-|+}password_changing_service
    The "+password_changing_service" option sets the `Password Changing Service' flag on the principal in the database, marking this principal as a password change service. "-password_changing_service" clears the flag. The default is "-password_changing_service".

    -randkey
    Sets the key for the principal to a random value (add_principal only). Cygnus Solutions recommends using this option for host keys.

    -pw password
    Sets the key of the principal to the specified string and does not prompt for a password (add_principal only). Cygnus Solutions does not recommend using this option.

    If you want to just use the default values, all you need to do is:

    kadmin: addprinc jennifer
    Enter password for principal jennifer@BLEEP.COM:  <= Type the password.
    Re-enter password for principal jennifer@BLEEP.COM:  <= Type it again.
    Principal "jennifer@BLEEP.COM" created.
    kadmin:
    

    If, on the other hand, you want to set up an account that expires on January 1, 2000, that uses a policy called "stduser", with a temporary password (which you want the user to change immediately), you would type the following. (Note: each line beginning with => is a continuation of the previous line.)

    
    kadmin: addprinc david -expire "1/1/2000 12:01am EST" -policy stduser 
    =>  +needchange 
    Enter password for principal david@BLEEP.COM:  <= Type the password.
    Re-enter password for principal
    david@BLEEP.COM:  <= Type it again.
    Principal "david@BLEEP.COM" created.
    kadmin:
    
    

    Deleting Principals

    To delete a principal, use the kadmin delete_principal command, which requires the "delete" administrative privilege. The syntax is:

    delete_principal [-force] principal
    

    delete_principal has the alias delprinc. The -force option causes delete_principal not to ask if you're sure. For example:

    kadmin: delprinc jennifer
    Are you sure you want to delete the principal
    "jennifer@BLEEP.COM"? (yes/no): yes
    Principal "jennifer@BLEEP.COM" deleted.
    Make sure that you have removed this principal from
    all ACLs before reusing.
    kadmin:
    

    Renaming Principals

    To rename a principal, use the kadmin rename_principal command, which requires both the "add" and "delete" administrative privileges. The syntax is:

    rename_principal [-force] old_principal new_principal
    

    The rename_principal command has the alias renprinc.

    For example:

    kadmin: renprinc test test2
    Are you sure you want to rename the principal
    "test@BLEEP.COM" to
    "test2@BLEEP.COM"? (yes/no): yes
    Principal "test@BLEEP.COM" renamed to
    "test2@BLEEP.COM".
    Make sure that you have removed "test@BLEEP.COM" from
    all ACLs before reusing.
    kadmin:
    

    Changing Passwords

    To change a principal's password use the kadmin change_password command, which requires the "modify" administrative privilege (unless the principal is changing his/her own password). The syntax is:

    change_password [options] principal
    

    The change_password option has the alias cpw. change_password takes the following options:

    -salt salttype
    Uses the specified salt for generating the key. Salt types are the same as for the add_principal command (see section Adding or Modifying Principals).

    -randkey
    Sets the key of the principal to a random value.

    -pw password
    Sets the password to the string password. Cygnus Solutions does not recommend using this option.

    For example:

    kadmin: cpw david
    Enter password for principal david@BLEEP.COM:  <= Type the new password.
    Re-enter password for principal david@BLEEP.COM:  <= Type it again.
    Password for david@BLEEP.COM changed.
    kadmin:
    

    Note that change_password will not let you change the password to one that is in the principal's password history.

    Policies

    Retrieving Policies

    To retrieve a policy, use the kadmin get_policy command, which requires the "inquire" administrative privilege. The syntax is:

    get_policy [-terse] policy
    

    The get_policy command has the alias getpol. For example:

    kadmin: get_policy admin
    Policy: admin
    Maximum password life: 180 days 00:00:00
    Minimum password life: 00:00:00
    Minimum password length: 6
    Minimum number of password character classes: 2
    Number of old keys kept: 5
    Reference count: 17
    kadmin:
    

    The reference count is the number of principals using that policy.

    The get_policy command has a -terse option, which lists each field as a quoted, tab-separated string. For example:

    kadmin: get_policy -terse admin
    admin   15552000        0       6       2       5       17
    kadmin:
    

    Retrieving the List of Policies

    You can retrieve the list of policies with the kadmin list_policies command, which requires the "list" privilege. The syntax is:

    list_policies [expression]
    

    where expression is a shell-style glob expression that can contain the characters *, ?, [, and ]. All policy names matching the expression are displayed. The list_policies command has the alias listpols. For example:

    kadmin:  listpols
    test-pol
    dict-only
    once-a-min
    test-pol-nopw
    
    kadmin:  listpols t*
    test-pol
    test-pol-nopw
    kadmin:
    

    Adding or Modifying Policies

    To add a new policy, use the kadmin add_policy command, which requires the "add" administrative privilege. The syntax is:

    add_policy [options] policy_name
    

    To modify attributes of a principal, use the kadmin modify_policy command, which requires the "modify" administrative privilege. The syntax is:

    modify_policy [options] policy_name
    

    add_policy has the alias addpol. modify_poilcy has the alias modpol.

    The add_policy and modify_policy commands take the following switches:

    -maxlife time
    Sets the maximum lifetime of a password to time.

    -minlife time
    Sets the minimum lifetime of a password to time.

    -minlength length
    Sets the minimum length of a password to length characters.

    -minclasses number
    Requires at least number of character classes in a password.

    -history number
    Sets the number of past keys kept for a principal to number.

    The character classes are:
    	- lower-case letters,
    	- upper-case letters,
    	- digits,
    	- punctuation, and
    	- all other characters (e.g., control characters).
    

    See section Date Format for details on the proper time format.

    Here is an example of adding a policy:

        kadmin:  addpol -minlength 8 -minclasses 3 -maxlife "30 days" paranoid
        kadmin:  getpol paranoid
        Policy: paranoid
        Maximum password life: 30 days 00:00:00
        Minimum password life: 0 days 00:00:00
        Minimum password length: 8
        Minimum number of password character classes: 3
        Number of old keys kept: 1
        Reference count: 0
    

    Deleting Policies

    To delete a policy, use the kadmin delete_policy command, which requires the "delete" administrative privilege. The syntax is:

    delete_policy policy_name
    

    The delete_policy command has the alias delpol. It prompts for confirmation before deletion. For example:

    kadmin: delete_policy guests
    Are you sure you want to delete the policy "guests"?
    (yes/no): yes
    Policy "guests" deleted.
    kadmin:
    

    Manipulating the Kerberos Database

    The following sections describe commands to manipulate the Kerberos database as a whole.

    Kdb5_util provides a means to create, delete, load, or dump a Kerberos database. It also includes a command to stash a copy of the master database key in a file on a KDC, so that the KDC can authenticate itself to the kadmind and krb5kdc daemons at boot time.

    Dumping a Kerberos Database to a File

    To dump a Kerberos database into a file, use the kdb5_util dump command on one of the KDCs. The syntax is:

    kdb5_util dump [-old] [-b6] [-ov] [-verbose] [filename
    [principals...]]
    

    The kdb5_util dump command takes the following options:

    -old
    causes the dump to be in the Kerberos 5 Beta 5 and earlier dump format ("kdb5_edit load_dump version 2.0").
    -b6
    causes the dump to be in the Kerberos 5 Beta 6 format ("kdb5_edit load_dump version 3.0").
    -ov
    causes the dump to be in ovsec_adm_export format.
    -verbose
    causes the name of each principal and policy to be printed as it is dumped.

    For example:

    shell% kdb5_util dump dumpfile
    shell%
    

    shell% kbd5_util dump -verbose dumpfile
    kadmin/admin@BLEEP.COM
    krbtgt/BLEEP.COM@BLEEP.COM
    kadmin/history@BLEEP.COM
    K/M@BLEEP.COM
    kadmin/changepw@BLEEP.COM
    shell%
    

    The following is a simple example from a Windows NT system:

    shell% kdb5_util dump c:\cygnus\KERBNET\lib\krb5kdc\dbdump
    

    If you specify which principals to dump, you must use the full principal, as in the following example. (The line beginning with => is a continuation of the previous line.):

    shell% kdb5_util dump -verbose dumpfile K/M@BLEEP.COM 
    => kadmin/admin@BLEEP.COM
    kadmin/admin@BLEEP.COM
    K/M@BLEEP.COM
    shell%
    

    Otherwise, the principals will not match those in the database and will not be dumped:

    shell% kdb5_util dump -verbose dumpfile K/M kadmin/admin
    shell%
    

    If you do not specify a dump file, kdb5_util will dump the database to the standard output.

    Restoring a Kerberos Database from a Dump File

    To restore a Kerberos database dump from a file, use the kdb5_util load command on one of the KDCs. The syntax is:

    kdb5_util load [-old] [-b6] [-ov] [-verbose] [-update]
    dumpfilename dbname [admin_dbname]
    

    The kdb5_util load command takes the following options:

    -old
    requires the dump to be in the Kerberos 5 Beta 5 and earlier dump format ("kdb5_edit load_dump version 2.0").
    -b6
    requires the dump to be in the Kerberos 5 Beta 6 format ("kdb5_edit load_dump version 3.0").
    -ov
    requires the dump to be in ovsec_adm_export format.
    -verbose
    causes the name of each principal and policy to be printed as it is dumped.
    -update
    causes records from the dump file to be updated in or added to the existing database.

    For example:

    shell% kdb5_util load dumpfile principal
    shell%
    

    shell% kdb5_util load -update dumpfile principal
    shell%
    

    If the database file exists, and the -update flag was not given, kdb5_util will overwrite the existing database.

    Creating a Stash File

    A stash file allows a KDC to authenticate itself to the database utilities, such as kadmin, kadmind, krb5kdc, and kdb5_util.

    To create a stash file, use the kdb5_util stash command. The syntax is:

    kdb5_util stash [-f keyfile]
    

    For example:

    shell% kdb5_util stash
    kdb5_util: Cannot find/read stored master key while reading master key
    kdb5_util: Warning: proceeding without master key
    Enter KDC database master key:  <= Type the KDC database master password.
    shell%
    

    If you do not specify a stash file, kdb5_util will stash the key in the file specified in your kdc.conf file.

    Creating and Destroying a Kerberos Database

    If you need to create a new Kerberos database, use the kdb5_util create command. The syntax is:

    kdb5_util create [-s]
    

    If you specify the `-s' option, kdb5_util will stash a copy of the master key in a stash file. (See section Creating a Stash File.) For example:

    shell% /usr/cygnus/kerbnet/sbin/kdb5_util -r BLEEP.COM create -s
    kdb5_util: No such file or directory while setting active database to '/krb5/principal'
    Initializing database '/usr/cygnus/kerbnet/lib/krb5kdc/principal' for
    => realm 'BLEEP.COM',
    master key name 'K/M@BLEEP.COM'
    You will be prompted for the database Master Password.
    It is important that you NOT FORGET this password.
    Enter KDC database master key:  <= Type the master password.
    Re-enter KDC database master key to verify:  <= Type it again.
    shell%
    

    Backing Up the Kerberos Database

    It is possible that the Kerberos database could become corrupted. If this happens on one of the slave KDCs, you might never notice, since the next automatic propagation of the database would install a fresh copy. However, if it happens to the master KDC, the corrupted database would be propagated to all of the slaves during the next propagation. For this reason, Cygnus Solutions recommends that you back up your Kerberos database regularly. Because the master KDC is continuously dumping the database to a file in order to propagate it to the slave KDCs, it is a simple matter to have a cron job periodically copy the dump file to a secure machine elsewhere on your network. (Of course, it is important to make the host where these backups are stored as secure as your KDCs, and to encrypt its transmission across your network.) Then if your database becomes corrupted, you can load the most recent dump onto the master KDC. (See section Restoring a Kerberos Database from a Dump File.)

    Application Servers

    If you need to install the KerbNet programs on an application server, please refer to the KerbNet Installation Guide. Once you have installed the software, you need to add that host to the Kerberos database (see section Adding or Modifying Principals), and generate a keytab for that host, that contains the host's key. You also need to make sure the host's clock is within your maximum clock skew of the KDCs.

    About Keytabs

    A keytab is a host's copy of its own keylist, which is analogous to a user's password. An application server that needs to authenticate itself to the KDC has to have a keytab that contains its own principal and key. Just as it is important for users to protect their passwords, it is equally important for hosts to protect their keytabs. You should always store keytab files on local disk, and make them readable only by root, and you should never send a keytab file over a network in the clear. Ideally, you should run the kadmin command or use the Admin GUI to create a keytab on the host on which the keytab is to reside.

    Keys and Key Version Numbers

    A keytab lists various principals and their keys. For a non-user principal, such as a service, the only way to get access to the key is through a keytab (unlike a user principal, which can access its key directly by using a password). To add a principal to a keytab so that its key can be used, you have to be able to get the principal's key from the Kerberos database. This process is called extraction and it not only places a hashed copy of the key in the keytab but it also changes the key so that any previously extracted copies in other keytabs become invalid.

    The next two sections of this chapter explain how to create keytabs using the Admin GUI and the command line.

    The Key Version Number (kvno) for a principal records how many times the key has been changed; the kvno of a newly-created principal is 0. Every time the principal is extracted from the database to a keytab, its key changes, and its kvno increments by 1.

    Manipulating Keytabs Using the Admin GUI

    Creating a Keytab

    1. Select Create from the Keytab menu.

    The Fileselect dialog opens.

    1. In the File text box, enter the keytab name. Specify the path for where you want the keytab to be stored, if you want to use a directory other than the current one (the current directory is listed above the File text box).

    2. Click OK to create the keytab, or Cancel to close the Fileselect dialog without creating a keytab.

    The Keytab Editing dialog appears.

    1. Enter principals into the keytab, as described in the next section.

    Modifying an existing Keytab

    1. Select Modify from the Keytab menu

    The Fileselect dialog opens.

    1. In the File text box, enter the name of the keytab you want to open, or select a keytab from the list.

      Specify the directory path if the keytab you want to modify is not stored in the directory listed above the File text box.

      The value in the Mask text box acts as a filter for the files listed in the Fileselect dialog; the list displays all the principals in the database that contain the Mask string.

      The Mask can contain the wildcard `*', which stands for any number of characters. Thus, the Mask `*.keytab' causes the list to display all files in the directory with the extension `/keytab'; the Mask `*' causes the list to display all the files in the directory.

    2. Click OK to open the selected keytab, or Cancel to close the Fileselect dialog without opening a keytab.

    When you click OK, the Keytab Editing dialog opens. This dialog lists all of the principals in the keytab. The kvno for each principal's key is listed in brackets next to the principal.

    1. To add a principal to the keytab, select that principal in the Principal List window, and click the Add Principals button in the Keytab Editing dialog.

    2. To delete one or more pricipals from the keytab, select the principal(s) in the Keytab Editing dialog and click the Delete Principals button.

    Manipulating Keytabs Using the Command Line

    Adding Principals to Keytabs

    To generate a keytab, or to add a principal to an existing keytab, use the ktadd command from kadmin, which requires the "inquire" administrative privilege. (If you use the -glob princ_exp option, it also requires the "list" administrative privilege.) The syntax is:

    ktadd [-k keytab] [-q] [principal | -glob princ_exp] [...]
    

    The ktadd command takes the following switches:

    -k keytab
    use keytab as the keytab file. Otherwise, ktadd will use the default keytab file (/etc/v5srvtab).

    -q
    run in quiet mode. This causes ktadd to display less verbose information.

    principal | -glob principal expression
    add principal, or all principals matching principal expression to the keytab. The rules for principal expression are the same as for the kadmin list_principals (see section Retrieving a List of Principals) command.

    For example:

    kadmin: ktadd host/daffodil.bleep.com@BLEEP.COM
    kadmin: Entry for principal host/daffodil.bleep.com@BLEEP.COM with
         kvno 2, encryption type DES-CBC-CRC added to keytab
         WRFILE:/etc/v5srvtab.
    kadmin:
    

    kadmin: ktadd -k /krb5/kadmind.keytab kadmin/admin kadmin/changepw
    kadmin: Entry for principal kadmin/admin@BLEEP.COM with
         kvno 3, encryption type DES-CBC-CRC added to keytab
         WRFILE:/krb5/kadmind.keytab.
    kadmin:
    

    On a Windows NT system the prefix `WRFILE:' must be used as in the following exaple:

    
    kadmin.local: ktadd -k WRFILE:C:\CYGNUS\KERBNET\LIB\KRB5KDC\KADM5.KEYTAB
    => kadmin/admin kadmin/changepw
    
    

    Removing Principals from Keytabs

    To remove a principal from an existing keytab, use the kadmin ktremove command. The syntax is:

    ktremove [-k keytab] [-q] principal [kvno | all | old]
    

    The ktremove command takes the following switches:

    -k keytab
    use keytab as the keytab file. Otherwise, ktremove will use the default keytab file (/etc/v5srvtab).

    -q
    run in quiet mode. This causes ktremove to display less verbose information.

    principal
    the principal to remove from the keytab. (Required.)

    kvno
    remove all entries for the specified principal whose Key Version Numbers match kvno.

    all
    remove all entries for the specified principal

    old
    remove all entries for the specified principal except those with the highest kvno.

    For example:

    kadmin: ktremove -k /krb5/kadmind.keytab kadmin/admin
    kadmin: Entry for principal kadmin/admin with kvno 3 removed
         from keytab WRFILE:/krb5/kadmind.keytab.
    kadmin:
    

    Listing Keytabs

    You can list the entries in a keytab by using the klist command with the -k option. For example:

    # klist -k
    Keytab name: /etc/v5srvtab
    KVNO Principal
    ---- ------------------------------------------------------------
       1 host/daffodil.bleep.com@BLEEP.COM
    

    Keytabs and Making Backups

    When you back up a secure host, you should exclude the host's keytab file from the backup. If someone obtained a copy of the keytab from a backup, that person could make any host masquerade as the host whose keytab was compromised. This could be particularly dangerous if the compromised keytab was from one of your KDCs. If the machine has a disk crash and the keytab file is lost, it is easy to generate another keytab file. (See the above sections for information on generating keytabs.) If you are unable to exclude particular files from backups, you should ensure that the backups are kept as secure as the host's administration password, i.e., the root or Administrator user.

    Clock Skew

    In order to prevent intruders from resetting their system clocks in order to continue to use expired tickets, KerbNet is set up to reject ticket requests from any host whose clock is not within the specified maximum clock skew of the KDC (as specified in the kdc.conf file). Similarly, hosts are configured to reject responses from any KDC whose clock is not within the specified maximum clock skew of the host (as specified in the krb5.conf file). The default value for maximum clock skew is 300 seconds (five minutes).

    Cygnus Solutions suggests that you add a line to client machines' /etc/rc files to synchronize the machine's clock to your KDC at boot time. On UNIX hosts, assuming you had a kdc called kerberos in your realm, this would be:

    gettime -s kerberos
    

    If the host is not likely to be rebooted frequently, you may also want to set up a cron job that adjusts the time on a regular basis.

    Getting Name Service Information Correct

    Several aspects of Kerberos rely on name service. In order for Kerberos to provide its high level of security, it is less forgiving of name service problems than some other parts of your network. It is important that your name service, whether /etc/hosts, NIS or Distributed Name Service (DNS), have the correct information.

    Each host's canonical name must be the fully-qualified host name (including the domain), and each host's IP address must reverse-resolve to the canonical name.

    Other than the localhost entry, make all entries in each machine's /etc/hosts or NIS map file in the following form:

    IP address      fully-qualified hostname        aliases
    

    Here is a sample /etc/hosts file:

    # this is a comment
    127.0.0.1       localhost localhost@bleep.com
    129.0.35.44       daffodil.bleep.com trillium wake-robin
    

    Additionally, on Solaris machines, you need to be sure the "hosts" entry in the file /etc/nsswitch.conf includes the source "dns" as well as "file".

    Finally, each host's keytab file must include a host/key pair for the host's canonical name. You can list the keys in a keytab file by issuing the command klist -k. (See section Listing Keytabs.)

    If you telnet to the host with a fresh credentials cache (ticket file), and then klist, the host's service principal should appear as host/fully-qualified-hostname@REALM_NAME.

    Configuring Your Firewall to Work With KerbNet

    If you need off-site users to be able to get Kerberos tickets in your realm, they must be able to get to your KDC. This requires either that you have a slave KDC outside your firewall, or you configure your firewall to allow UDP requests into to at least one of your KDCs, on whichever port the KDC is running. (The default is port 88; other ports may be specified in the KDC's kdc.conf file.) Similarly, if you need off-site users to be able to change their passwords in your realm, they must be able to get to your Kerberos admin server. The default port for the admin server is 749.

    If your on-site users inside your firewall will need to get to KDCs in other realms, you will also need to configure your firewall to allow outgoing TCP and UDP requests on port 88. Additionally, if they will need to get to any Kerberos V4 KDCs, you will also need to allow TCP and UDP requests on port 750. (See the document Upgrading to KerbNet from Kerberos V4 for additional information about using Kerberos V4 and KerbNet concurrently.) If your on-site users inside your firewall will need to get to Kerberos admin servers in other realms, you will also need to allow outgoing TCP and UDP requests to port 749.

    If any of your KDCs is outside your firewall, you will need to allow kprop requests to get through to the remote KDC. Kprop uses the krb5_prop service on port 754 (tcp).

    If you need your off-site users to have access to machines inside your firewall, you need to allow TCP connections from their off-site hosts on the appropriate ports for the programs they will be using. The following lines from /etc/services show the default port numbers for the KerbNet programs:

    ftp           21/tcp           # Kerberos ftp and telnet use the
    telnet        23/tcp           # default ports
    kerberos      88/udp    kdc    # Kerberos V5 KDC
    kerberos      88/tcp    kdc    # Kerberos V5 KDC
    klogin        543/tcp          # Kerberos authenticated rlogin
    kshell        544/tcp   cmd    # and remote shell
    kerberos-adm  749/tcp          # Kerberos 5 admin/changepw
    kerberos-adm  749/udp          # Kerberos 5 admin/changepw
    krb5_prop     754/tcp          # Kerberos slave propagation
    eklogin       2105/tcp         # Kerberos auth. & encrypted rlogin
    krb524        4444/tcp         # Kerberos 5 to 4 ticket translator
    

    By default, KerbNet telnet and ftp use the same ports as the standard telnet and ftp programs, so if you already allow telnet and ftp connections through your firewall, the KerbNet versions will get through as well. If you do not already allow telnet and ftp connections through your firewall, but need your users to be able to use KerbNet telnet and ftp, you can either allow ftp and telnet connections on the standard ports, or switch these programs to non-default port numbers and allow ftp and telnet connections on those ports to get through.

    KerbNet rlogin uses the klogin service, which by default uses port 543. Encrypted KerbNet rlogin uses uses the eklogin service, which by default uses port 2105.

    KerbNet rsh uses the kshell service, which by default uses port 544. However, the server must be able to make a TCP connection from the kshell port to an arbitrary port on the client, so if your users are to be able to use rsh from outside your firewall, the server they connect to must be able to send outgoing packets to arbitrary port numbers. Similarly, if your users need to run rsh from inside your firewall to hosts outside your firewall, the outside server needs to be able to connect to an arbitrary port on the machine inside your firewall. Because KerbNet rcp and krdist use rsh, the same issues apply to these programs. If you need to use rsh (or rcp or krdist) through your firewall and are concerned with the security implications of allowing connections to arbitrary ports, Cygnus Solutions suggests that you have rules that specifically name these applications and, if possible, list the allowed hosts.

    A reasonably good cookbook for configuring firewalls is available by FTP from ftp.livingston.com, in the location: /pub/firewall/firewall-1.1.ps.Z. The book UNIX System Security, by David Curry, is also a good starting point.

    Configuration Files

    krb5.conf

    The krb5.conf file contains Kerberos configuration information, including the locations of KDCs and admin servers for the Kerberos realms of interest, defaults for the current realm and for Kerberos applications, and mappings of hostnames onto Kerberos realms. Normally, you should install your krb5.conf file in the directory /etc. You can override the default location by setting the environment variable `KRB5_CONFIG'.

    The krb5.conf file is set up in the style of a Windows INI file. Sections are headed by the section name, in square brackets. Each section may contain zero or more relations, of the form:

    foo = bar
    

    or

    fubar = {
            foo = bar
            baz = quux
    }
    

    The krb5.conf file may contain any or all of the following seven sections:

    libdefaults
    Contains default values used by the Kerberos V5 library.

    appdefaults
    Contains default values used by Kerberos V5 applications.

    realms
    Contains subsections keyed by Kerberos realm names. Each subsection describes realm-specific information, including where to find the Kerberos servers for that realm.

    domain_realm
    Contains relations which map domain names and subdomains onto Kerberos realm names. This is used by programs to determine what realm a host should be in, given its fully qualified domain name.

    logging
    Contains relations which determine how Kerberos programs are to perform logging.

    capaths
    Contains the authentication paths used with direct (nonhierarchical) cross-realm authentication. Entries in this section are used by the client to determine the intermediate realms which may be used in cross-realm authentication. It is also used by the end-service when checking the transited field for trusted intermediate realms.

    kdc
    For a KDC, may contain the location of the kdc.conf file.

    [libdefaults]

    The libdefaults section may contain any of the following relations:

    default_realm
    Identifies the default Kerberos realm for the client. Set its value to your Kerberos realm.

    default_tgs_enctypes
    Identifies the supported list of session key encryption types that should be returned by the KDC. The list may be delimited with commas or whitespace. Currently, the only supported encryption type is "des-cbc-crc". Support for other encryption types is planned in the future.

    default_tkt_enctypes
    Identifies the supported list of session key encryption types that should be requested by the client. The format is the same as for default_tkt_enctypes. Again, the only supported encryption type is "des-cbc-crc".

    checksum_type
    Used for compatability with DCE security servers which do not support the default CKSUMTYPE_RSA_MD5 used by this version of Kerberos. A value of 1 indicates the default checksum type. Use a value of 2 to use the CKSUMTYPE_RSA_MD4 instead. This applies to DCE 1.1 and earlier.

    ccache_type
    Use this parameter on systems which are DCE clients, to specify the type of cache to be created by kinit, or when forwarded tickets are received. DCE and Kerberos can share the cache, but some versions of DCE do not support the default cache as created by this version of Kerberos. Use a value of 1 on DCE 1.0.3a systems, and a value of 2 on DCE 1.1 systems.

    renew_lifetime
    If a renew_lifetime is specified and non-zero, then the RENEWABLE option on the ticket will be set, and the value of the configuration variable will be the the renewable lifetime. The default is not to set the RENEWABLE option.

    forwardable
    If forwardable is specified, the FORWARDABLE option on the ticket will be set if and only if the variable is "y", "yes", "true", "t", "1", or "on", case insensitive. The default is not to set the FORWARDABLE option.

    proxiable
    If proxiable is specified, the PROXIABLE option on the ticket will be set if and only if the variable is "y", "yes", "true", "t", "1", or "on", case insensitive. The default is not to set the PROXIABLE option.

    verify_ap_req_nofail
    This is only used by login and Xdm. It is an additional bit of protection against name service attacks on hosts that use a `host' key to verify the TGT the user decrypts on login. We recommend this be set on such machines, particularly if they are on insecure networks. It must not be set on machines without a keytab as it will prevent users from being able to log in.

    [appdefaults]

    Each tag in the [appdefaults] section names a Kerberos V5 application. The value of the tag is a subsection with relations that define the default behaviors for that application.

    For example:

    [appdefaults]
        rlogin = {
            forwardable = true
            forward = true
            encrypt = true
        }
        telnet = {
            forward = true
            encrypt = true
            autologin = true
        }
    

    The list of specifiable options for each application may be found in that application's man pages.

    [realms]

    Each tag in the [realms] section of the file is the name of a Kerberos realm. The value of the tag is a subsection with relations that define the properties of that particular realm. For each realm, the following tags may be specified in the realm's subsection:

    kdc
    The name of a host running a KDC for that realm. An optional port number (separated from the hostname by a colon) may be included.

    admin_server
    Identifies the host where the administration server is running. Typically this is the master Kerberos server.

    [domain_realm]

    The [domain_realm] section provides a translation from a domain name or hostname to a Kerberos realm name. The tag name can be a host name, or a domain name, where domain names are indicated by a prefix of a period (`.'). The value of the relation is the Kerberos realm name for that particular host or domain. Host names and domain names should be in lower case.

    If no translation entry applies, the host's realm is considered to be the hostname's domain portion converted to upper case. For example, the following [domain_realm] section:

    [domain_realm]
        bleep.com = BLEEP.COM
        crash.bleep.com = TEST.BLEEP.COM
        fubar.org = FUBAR.ORG
    

    maps crash.bleep.com into the TEST.BLEEP.COM realm. All other hosts in the bleep.com domain will map by default to the BLEEP.COM realm, and all hosts in the fubar.org domain will map by default into the FUBAR.ORG realm. Note the entries for the hosts bleep.com and fubar.org. Without these entries, these hosts would be mapped into the Kerberos realms `COM' and `ORG', respectively.

    [logging]

    The [logging] section indicates how a particular entity is to perform its logging. The relations in this section assign one or more values to the entity name. Currently, the following entities are used:

    kdc
    These entries specify how the KDC is to perform its logging.

    admin_server
    These entries specify how the administrative server is to perform its logging.

    default
    These entries specify how to perform logging in the absence of explicit specifications otherwise.

    Values are of the following forms:

    FILE=<filename>

    FILE:<filename>
    This value causes the entity's logging messages to go to the specified file. If the `=' form is used, the file is overwritten. If the `:' form is used, the file is appended to.

    STDERR
    This value causes the entity's logging messages to go to its standard error stream.

    CONSOLE
    This value causes the entity's logging messages to go to the console, if the system supports it.

    DEVICE=<devicename>
    This causes the entity's logging messages to go to the specified device.

    SYSLOG[:<severity>[:<facility>]]
    This causes the entity's logging messages to go to the system log.

    The severity argument specifies the default severity of system log messages. This may be any of the following severities supported by the syslog(3) call, minus the LOG_ prefix: LOG_EMERG, LOG_ALERT, LOG_CRIT, LOG_ERR, LOG_WARNING, LOG_NOTICE, LOG_INFO, and LOG_DEBUG. For example, a value of `CRIT' would specify LOG_CRIT severity.

    The facility argument specifies the facility under which the messages are logged. This may be any of the following facilities supported by the syslog(3) call minus the LOG_ prefix: LOG_KERN, LOG_USER, LOG_MAIL, LOG_DAEMON, LOG_AUTH, LOG_LPR, LOG_NEWS, LOG_UUCP, LOG_CRON, and LOG_LOCAL0 through LOG_LOCAL7.

    If no severity is specified, the default is ERR. If no facility is specified, the default is AUTH.

    In the following example, the logging messages from the KDC will go to the console and to the system log under the facility LOG_DAEMON with default severity of LOG_INFO; and the logging messages from the administrative server will be appended to the file /var/adm/kadmin.log and sent to the device /dev/tty04.

    [logging]
        kdc = CONSOLE
        kdc = SYSLOG:INFO:DAEMON
        admin_server = FILE:/var/adm/kadmin.log
        admin_server = DEVICE=/dev/tty04
    

    [capaths]

    In order to perform direct (non-hierarchical) cross-realm authentication, a database is needed to construct the authentication paths between the realms. This section defines that database.

    A client will use this section to find the authentication path between its realm and the realm of the server. The server will use this section to verify the authentication path used be the client, by checking the transited field of the received ticket.

    There is a tag for each participating realm, and each tag has subtags for each of the realms. The value of the subtags is an intermediate realm which may participate in the cross-realm authentication. The subtags may be repeated if there is more then one intermediate realm. A value of "." means that the two realms share keys directly, and no intermediate realms should be allowd to participate.

    There are n squared possible entries in this table, but only those entries which will be needed on the client or the server need to be present. The client needs a tag for its local realm, with subtags for all the realms of servers it will need to authenticate with. A server needs a tag for each realm of the clients it will serve.

    For example, ANL.GOV, PNL.GOV, and NERSC.GOV all wish to use the ES.NET realm as an intermediate realm. ANL has a sub realm of TEST.ANL.GOV which will authenticate with NERSC.GOV but not PNL.GOV. The [capath] section for ANL.GOV systems would look like this:

    [capaths]
        ANL.GOV = {
            TEST.ANL.GOV = .
            PNL.GOV = ES.NET
            NERSC.GOV = ES.NET
            ES.NET = .
        }
        TEST.ANL.GOV = {
            ANL.GOV = .
        }
        PNL.GOV = {
            ANL.GOV = ES.NET
        }
        NERSC.GOV = {
            ANL.GOV = ES.NET
        }
        ES.NET = {
            ANL.GOV = .
        }
    

    The [capath] section of the configuration file used on NERSC.GOV systems would look like this:

    [capaths]
        NERSC.GOV = {
            ANL.GOV = ES.NET
            TEST.ANL.GOV = ES.NET
            TEST.ANL.GOV = ANL.GOV
            PNL.GOV = ES.NET
            ES.NET = .
        }
        ANL.GOV = {
            NERSC.GOV = ES.NET
        }
        PNL.GOV = {
            NERSC.GOV = ES.NET
        }
        ES.NET = {
            NERSC.GOV = .
        }
        TEST.ANL.GOV = {
            NERSC.GOV = ANL.GOV
            NERSC.GOV = ES.NET
        }
    

    In the above examples, the ordering is not important, except when the same subtag name is used more then once. The client will use this to determing the path. (It is not important to the server, since the transited field is not sorted.)

    This feature is not currently supported by DCE. DCE security servers can be used with Kerberized clients and servers, but versions prior to DCE 1.1 did not fill in the transited field, and should be used with caution.

    [kdc]

    The [kdc] section is used to define configuration information necessary for a KDC to find the KDC configuration file (kdc.conf) if it is not in the default location. The only tag used in this section would be `profile', which would be set to the location of the KDC configuration file.

    Sample krb5.conf File

    Here is an example of a generic krb5.conf file:

    [libdefaults]
        ticket_lifetime = 600
        default_realm = BLEEP.COM
        default_tkt_enctypes = des-cbc-crc
        default_tgs_enctypes = des-cbc-crc
    
    [realms]
        BLEEP.COM = {
            kdc = kerberos.bleep.com
            kdc = kerberos-1.bleep.com
            kdc = kerberos-2.bleep.com
            admin_server = kerberos.bleep.com
            default_domain = bleep.com
        }
        FUBAR.ORG = {
            kdc = kerberos.fubar.org
            kdc = kerberos-1.fubar.org
            admin_server = kerberos.fubar.org
        }
    
    [domain_realm]
        bleep.com = BLEEP.COM
    
    [logging]
        kdc = FILE:/usr/cygnus/kerbnet/lib/krb5kdc/kdc.log
        admin_server = FILE:/usr/cygnus/kerbnet/lib/krb5kdc/kadmin.log
    
    

    l

    kdc.conf

    The kdc.conf file contains KDC configuration information, including defaults used when issuing Kerberos tickets. Normally, you should install your kdc.conf file in the directory /usr/cygnus/kerbnet/lib/krb5kdc. You can override the default location by setting the environment variable `KRB5_KDC_PROFILE'.

    The kdc.conf file is set up in the same format as the krb5.conf file. (See section krb5.conf.) The kdc.conf file may contain any or all of the following two sections:

    kdcdefaults
    Contains default values for overall behavior of the KDC.

    realms
    Contains subsections keyed by Kerberos realm names. Each subsection describes realm-specific information, including where to find the Kerberos servers for that realm.

    [kdcdefaults]

    The following relation is defined in the [kdcdefaults] section:

    kdc_ports
    This relation lists the ports on which the Kerberos server should listen by default. This list is a comma separated list of integers. If this relation is not specified, the compiled-in default is usually port 88 (the assigned Kerberos port) and port 750 (the port used by Kerberos V4).

    [realms]

    Each tag in the [realms] section of the file names a Kerberos realm. The value of the tag is a subsection where the relations in that subsection define KDC parameters for that particular realm.

    For each realm, the following tags may be specified in the [realms] subsection:

    acl_file
    (String.) Location of the access control list (acl) file that kadmin uses to determine which principals are allowed which permissions on the database. The default is /usr/cygnus/kerbnet/lib/krb5kdc/kadm5.acl.

    admin_keytab
    (String.) Location of the keytab file that kadmin uses to authenticate to the database. The default is
    /usr/cygnus/kerbnet/lib/krb5kdc/kadm5.keytab.

    database_name
    (String.) Location of the Kerberos database for this realm. The default is /usr/cygnus/kerbnet/lib/krb5kdc/principal.

    default_principal_expiration
    (Absolute time string.) Specifies the default expiration date of principals created in this realm. No entry is the same as never.

    default_principal_flags
    (Flag string.) Specifies the default attributes of principals created in this realm.

    This is the list of flags and how to set them to different from the default case:

    -postdateable
    -forwardable
    -tgt-based
    -renewable
    -proxiable
    -dup-skey
    -allow-tickets
    -service
    +preauth
    +hwauth
    +pwchange
    +pwservice
    

    The argument is a list of flags, preceded by + to indicate set, and - to indicate unset, separated by spaces, tabs, or commas. For example:

    default_principal_flags = -forwardable -renewable +preauth
    

    This would disallow forwardable tickets, disallow renewable tickets and require preauthentication for all priciples by default.

    dict_file
    (String.) Location of the dictionary file containing strings that are not allowed as passwords. The default is
    /usr/cygnus/kerbnet/lib/krb5kdc/kadm5.dict.

    encryption_type
    (Encryption type string.) Specifies the encryption type used for this realm. Only "des-cbc-crc" is supported at this time.

    kadmind_port
    (Port number.) Specifies the port that the kadmind daemon is to listen for this realm. The assigned port for kadmind is 749.

    key_stash_file
    (String.) Specifies the location where the master key has been stored (via kdb5_util stash). The default is /usr/cygnus/kerbnet/lib/krb5kdc/.k5.REALM, where REALM is the Kerberos realm.

    kdc_ports
    (String.) Specifies the list of ports that the KDC is to listen to for this realm. By default, the value of kdc_ports as specified in the [kdcdefaults] section is used.

    master_key_name
    (String.) Specifies the name of the master key.

    master_key_type
    (Key type string.) Specifies the master key's key type. Only "des-cbc-crc" is supported at this time.

    max_life
    (Delta time string.) Specifes the maximum time period for which a ticket may be valid in this realm.

    max_renewable_life
    (Delta time string.) Specifies the maximum time period during which a valid ticket may be renewed in this realm.

    profile
    (String.) Location of the Kerberos V5 configuration file, if different from the default (/etc/krb5.conf).

    supported_enctypes
    List of key:salt strings. Specifies the default key/salt combinations of principals for this realm. Since only the encryption type "des-cbc-crc" is supported, but both normal and V4 salt types are supported you should set this tag to `des-cbc-crc:normal des-cbc-crc:v4'.

    Sample kdc.conf File

    Here's an example of a kdc.conf file:

    [kdcdefaults]
        kdc_ports = 88
    
    [realms]
        BLEEP.COM = {
            kadmind_port = 749
            max_life = 10h 0m 0s
            max_renewable_life = 7d 0h 0m 0s
            master_key_type = des-cbc-crc
            supported_enctypes = des-cbc-crc:normal des-cbc-crc:v4
        }
    
    

    Updates

    Because the directory into which KerbNet installs itself contains the release name, it is easy to install a new release of KerbNet, and to de-install an old one. If you have a problem with a new release, it is equally easy to revert to the earlier release. These procedures will also work if you are updating from any other version of Kerberos V5.

    Updating KDCs

    To update a KDC from an earlier version of KerbNet or of Kerberos V5, you need to do the following:

    1. Install the new software.
    2. Copy your kdc.conf file and stash file from the old installation to the new one. For example, if you were upgrading from KerbNet version 1.1 to version 1.2, you would have to copy these files from the directory /usr/cygnus/kerbnet-1.1 to the directory /usr/cygnus/kerbnet-1.2. Be sure the new copy of the stash file has the correct name. (The default is .k5.REALM, where REALM is your realm name, unless you have specified something different in your kdc.conf file.)
    3. Create a dump of the old database, using whichever old command you used with that release (e.g., the kdb5_dump command).
    4. Load the dumpfile into the new database in the new location, using the kdb5_util load command. Be sure to give load the argument for the correct dump format.
    5. Change any symbolic links you have (e.g., /usr/kerbnet) so that they point to the new installation.

    Updating Clients and Application Servers

    To update a client or application server, you need only to install the new release and change any symbolic links to point to the new programs. Other than any functionality changes in the programs, the upgrade should be completely user-transparent.

    Support

    Supported Functionalities

    The following functionalities are supported for KerbNet, provided that they are installed and used as described in the documentation.

    Cygnus Solutions supports only DES-CRC keys. Other encryption types are not supported at this time.

    Directly-keyed cross-realm authentication is supported. Hierarchal cross-realm authentication is not supported.

    System Administrator Commands

    kdb5_util

    creating a database is supported. Loading and dumping a Kerberos database in current, V4, old V5 (beta 5 and earlier), V5 beta 6, or OpenVision ovsec_adm_export format is supported. Creating a stash file is supported.

    kadmin and kadmin.local

    Use of local (kadmin.local) and remote (kadmin) client is supported. Command-line specification of Kerberos Realm, principal, credentials cache location, keytab, password, admin server and port, and specific query is supported for the remote client. Command-line specification of Kerberos realm, principal, database name, encryption type and salt type, and authentication using the database master password is supported for the local client. Execution of a single query or of multiple queries through the command's subshell is supported.

    For both clients, the following functions are supported:

    Adding or modifying principals including: explicit setting of password (specified or random; add only), expiration dates for principal and password, setting of maximum ticket life and maximum renewable life, key version number, policy used by that principal, clearing of policy from principal (modify only) and need to change password flag is supported.

    Allowing/disallowing a principal to obtain: any tickets, postdated tickets, forwardable tickets, renewable tickets, proxiable tickets, user-to-user authentication, service tickets, ticket-granting service tickets, and password changing service tickets is supported.

    Requiring timestamp preauthentication or hardware preauthentication for a principal is supported.

    Renaming, deletion, passward changing (random or specified) of principals is supported.

    Creation and modification of policies, including minimum and maximum password lifetimes, minimum length and number of character classes in password, and number of previous passwords stored is supported.

    Retrieval and listing of principals and policies from the database is supported.

    Addition and deletion of principals from V5 keytabs is supported. Specific removal of keys by specific key version number (kvno), and removal of all but the most recent kvno is supported.

    kprop and kpropd

    Encrypted propagation of a database dump from the master KDC to slave KDCs via the kpropd daemon is supported.

    Login and User Admin Commands

    kinit

    Obtaining of Kerberos V5 tickets via a user-entered password or a keytab for a default or specified principal is supported. Specification of credentials cache location and ticket lifetime is supported. Obtaining of forwardable, proxiable, renewable, and/or postdated tickets is supported. Renewing of renewable tickets and validation of postdated tickets is supported. Hardware preauthentication via challenge/response on SNK4 device from Digital Pathways is supported. Configuring default behavior regarding proixable or forwardable tickets via the krb5.conf file is supported.

    klist

    Listing of Kerberos V5 tickets is supported. Specification of credentials cache or keytab file is supported. Optional listing of encryption types, flags, time entry timestamps, and encryption key values is supported. Silent behavior (suppression of output to stdout) is supported.

    kdestroy

    Destruction of Kerberos tickets is supported. Specification of credentials cache location is supported (required for a Kerberos V4 ticket file). Suppression of audible signal upon failure to destroy tickets is supported.

    kpasswd

    Changing of Kerberos passwords is supported. Specification of Kerberos principal is supported.

    login.krb5

    Logging in on the console of users who appear in /etc/passwd with their Kerberos passwords, along with issuance of Kerberos V5 tickets, and authentication to the local machine is supported. Configuration of issuance of tickets via krb5.conf file is supported.

    Issuance of AFS tokens is supported only for customers who purchase AFS support for KerbNet. Use of the login.krb5 program at the command prompt as a means of switching user ID is not supported.

    xdm

    Logging in under X of users who appear in /etc/passwd with their kerberos password, along with issuance of Kerberos V5 tickets, and authentication to the local machine is supported. Rebuilding xdm from source code is supported only if the X installation matches that required by the configure scripts.

    The XDMCP protocol is not supported; remote displays must be explicitly listed in configuration file.

    User Commands

    rsh and kshd

    Kerberos authentication to remote host running KerbNet kshd and execution of remote command(s) is supported. Specification of Kerberos realm, encryption or non-encryption, forwarding or non-forwarding of forwardable tickets, forwardability or non-forwardability of forwarded tickets, and/or username on the remote host is supported. Configuring default behavior regarding encryption, forwarding, and forwardability of forwarded tickets via the krb5.conf file is supported.

    For the kshd daemon, specification of required Kerberos V5 and/or Kerberos V4 authentication, required checksums for Kerberos V5 (not compatible with earlier versions (beta 6 and earlier) of Kerberos V5), and rejection of non-Kerberos authenticated connections is supported.

    Other functionalities are supported only to the extent that behavior is consistent with non-Kerberos, non-vendor-enhanced versions of these programs.

    rcp

    Kerberos V5 authentication to remote host(s) running KerbNet kshd and copying of file(s) to and/or from remote host(s) is supported. Specification of Kerberos realm and encryption or non-encryption is supported. Configuring default behavior regarding encryption via the krb5.conf file is supported.

    Other functionalities are supported only to the extent that behavior is consistent with non-Kerberos, non-vendor-enhanced versions of these programs.

    telnet and telnetd

    Kerberos V5 authentication to remote host running KerbNet telnetd and connection to that remote host using the TELNET protocal is supported. Specification of Kerberos realm, encryption or non-encryption, forwarding or non-forwarding of forwardable tickets, forwardability or non-forwardability of forwarded tickets, username on the remote host, or autologin or non-autologin is supported.

    Enabling/disabling of authentication, encryption (on input and/or output), and autologin at the telnet> prompt is supported.

    Configuring default behavior regarding encryption, forwarding, forwardability of forwarded tickets, and autologin via the krb5.conf file is supported.

    For the telnetd daemon, specification of required Kerberos authentication is supported.

    Other functionalities are supported only to the extent that behavior is consistent with non-Kerberos, non-vendor-enhanced versions of these programs.

    rlogin and klogind

    Kerberos V5 authentication to remote host running KerbNet klogind and connection to that remote host using the rlogin protocal is supported. Specification of Kerberos realm, encryption or non-encryption, forwarding or non-forwarding of forwardable tickets, forwardability or non-forwardability of forwarded tickets, and username on the remote host is supported.

    Configuring default behavior regarding encryption, forwarding, and forwardability of forwarded tickets via the krb5.conf file is supported.

    For the klogind daemon, specification of required Kerberos V5 and/or Kerberos V4 authentication, required checksums for Kerberos V5 (not compatible with earlier versions (beta 6 and earlier) of Kerberos V5), and rejection of non-Kerberos authenticated connections is supported.

    Other functionalities are supported only to the extent that behavior is consistent with non-Kerberos, non-vendor-enhanced versions of these programs.

    ftp and ftpd

    Kerberos V5 authentication to remote host running KerbNet ftpd, connection to the remote host using the FTP protocol, and file transfer to or from the remote host using the FTP protocol is supported. Specification of Kerberos realm and forwarding of tickets is supported. Specification of data integrity checking (via cryptographic checksum) and/or encryption at the ftp> prompt is supported.

    For the ftpd daemon, specification of the Kerberos Configuration (krb5.conf) file, and required Kerberos authentication is supported.

    Other functionalities are supported only to the extent that behavior is consistent with non-Kerberos, non-vendor-enhanced versions of these programs.

    ksu

    Kerberos V5 authentication and switching of user ID by ksu to the target user if the requesting user is listed in the target user's ~/.k5login file is supported. Execution of specific commands through ksu if the requesting user is listed in the target user's ~/.k5login or ~/.k5users file is supported. Kerberos V5 preauthentication via challenge/response on SNK4 device from Digital Pathways is supported.

    Using send-pr

    As with the other KerbNet binaries, the send-pr program is installed in the directory /usr/cygnus/kerbnet/bin.

    Before using send-pr for the first time, you need to install your customer support ID into the program, by typing the command:

    shell% install-sid customerID
    

    replacing customerID with your customer ID, which your sales representative will supply.

    The send-pr program enters the problem report into our Problem Report Management System (PRMS), which automatically assigns it to the engineer best able to help you with problems in the assigned category. The engineer will work with you via email, telephone, or both, and all email related to this Problem Report will be tracked by PRMS for future reference. If the engineer does not reply to you after a certain time, a reminder is automatically generated. If you need to talk to someone else in our organization about the problem (e.g., if the engineer gets hit by a truck), we can find out what the current state is through the PR number. Cygnus Solutions uses PRMS for almost all of the real problems we handle.

    The send-pr program will try to intelligently fill in as many fields as it can. You need to choose the category, class, severity, and priority of the problem, as well as giving us as much information as you can about its exact nature.

    The PR category will be one of:

    kerberos        kerbnet         doc             help-request
    info-request    install         query-pr        id-request
    send-pr
    

    In general, if specific knowledge about Kerberos is requried to answer a PR, use the kerberos or doc categories. The install category is for problems retrieving the code off the media (e.g., the data on a tape seems to be corrupted.) Questions about the installation procedures described in this document would fall under the category kerberos. The help-request and info-request categories are for general questions about your contract, or other issues not necessarily related to KerbNet. Use query-pr to receive a current copy of your Problem Report, id-request if you need a customer ID, and send-pr if you're having trouble using send-pr. If your question is related to KerbNet and you're not sure what the most appropriate category should be, use kerberos. The engineer can change the category if necessary.

    The class can be sw-bug, doc-bug, change-request, or support. The first two are exactly as their names imply. The change-request class is to inform us of changes, such as new email addresses or new contact information. The support class is intended for general questions about using the KerbNet clients or libraries.

    The severity of the problem indicates the problem's impact on the usability of the KerbNet software package. If a problem is critical, that means the product, component or concept is completely non-operational, or some essential functionality is missing, and no workaround is known. A serious problem is one in which the product, component or concept is not working properly or significant functionality is missing. Problems that would otherwise be considered critical are rated serious when a workaround is known. A non-critical problem is one that is indeed a problem, but one that is having a minimal affect on your ability to use KerbNet. E.g., The product, component or concept is working in general, but lacks features, has irritating behavior, does something wrong, or doesn't match its documentation. The default severity is serious.

    The priority indicates how urgent this particular problem is in relation to your work. Note that low priority does not imply low importance. Cygnus Solutions considers all problems important, and encourages its customers to be realistic about priority ratings. A priority of high means a solution is needed as soon as possible. A priority of medium means the problem should be solved no later than the next release. A priority of low means the problem should be solved in a future release, but it is not important to your work how soon this happens. The default priority is medium.

    Note that a given severity does not necessarily imply a given priority. For example, a non-critical problem might still have a high priority if you are faced with a hard deadline. Conversely, a serious problem might have a low priority if the feature it is disabling is one that you do not need.

    The release is as labeled on the software that was shipped. e.g., kerbnet-1.2. It is important that you tell us which release you are using, and whether or not you have made any private changes.

    Bug reports that include proposed fixes are especially welcome. If you include proposed fixes, please send them using either context diffs (`diff -c') or unified diffs (`diff -u').

    l

    A sample filled-out form from a company named "Toasters, Inc." might look like this:

    To: bugs@cygnus.com
    Subject: "KDC reply did not match expectations" error
    From: joe.smith@toasters.com
    Reply-To: joe.smith@toasters.com
    X-send-pr-version: 3.97-96q1
    
    >Submitter-Id:	toastersinc
    >Confidential:	yes
    >Originator:	Joe Smith  (+1 415 903 1400)
    >Organization:
    -----
    Joe Smith			joe.smith@toasters.com
    Toasters, Inc.
             "The best UI in the world"
    
    >Synopsis:	"KDC reply did not match expectations" error message
    >Severity:	non-critical
    >Priority:	low
    >Category:	kerberos
    >Class:		sw-bug
    >Release:	kerbnet-1.2
    >Environment:
    NetBSD viola 1.1 NetBSD 1.1 (ATHENAADP) #0: Tue May 21 00:31:42 EDT 1996
    i386
    System:		Intel P166
    Architecture:	NetBSD
    
    >Description:
    	<description of problem goes here>
            Getting "KDC reply did not match expectations" message.  This
            does not seem to be affecting anything else.
    
    >How-To-Repeat:
    	
    	<If the Problem Report is marked "Confidential: yes",>
    	<it will not be available to anyone but our engineers,>
    	<please contact us if you are concerned about sensitive source>
    	<code.>
            It happens when I type kinit.
    
    >Fix:
    	<If you have already found a correct way to stop this problem,>
    	<please let us know!>
            None.  Sorry.
    

    l

    If the send-pr program does not work for you, you can use the following template instead:

    To: bugs@cygnus.com
    Subject:
    From: 
    Reply-To: 
    X-send-pr-version: none (typed manually)
    
    >Submitter-Id:  
    >Originator:    
    >Organization:
            <organization of PR author (multiple lines)>
    >Confidential:  <[ yes | no ] (one line)>
    >Synopsis:  <synopsis of the problem (one line)>
    >Severity:  <[ non-critical | serious | critical ] (one line)>
    >Priority:  <[ low | medium | high ] (one line)>
    >Category:  <name of the product (one line)>
    >Class:     <[ sw-bug | doc-bug | change-request | support ] (one line)>
    >Release:      cns-9?q?
    >Environment:
            <machine, os, target, libraries (multiple lines)>
    System: 
    Architecture: 
    
    
    >Description:
        <precise description of the problem (multiple lines)>
    >How-To-Repeat:
        <code/input/activities to reproduce the problem (multiple lines)>
    >Fix:
        <how to correct or work around the problem, if known (multiple lines)>
    

    Appendix

    Kerberos Error Messages

    Kerberos V5 Library Error Codes

    This is the Kerberos v5 library error code table. Protocol error codes are ERROR_TABLE_BASE_krb5 + the protocol error code number; other error codes start at ERROR_TABLE_BASE_krb5 + 128.

    1. KRB5KDC_ERR_NONE: No error
    2. KRB5KDC_ERR_NAME_EXP: Client's entry in database has expired
    3. KRB5KDC_ERR_SERVICE_EXP: Server's entry in database has expired
    4. KRB5KDC_ERR_BAD_PVNO: Requested protocol version not supported
    5. KRB5KDC_ERR_C_OLD_MAST_KVNO: Client's key is encrypted in an old master key
    6. KRB5KDC_ERR_S_OLD_MAST_KVNO: Server's key is encrypted in an old master key
    7. KRB5KDC_ERR_C_PRINCIPAL_UNKNOWN: Client not found in Kerberos database
    8. KRB5KDC_ERR_S_PRINCIPAL_UNKNOWN: Server not found in Kerberos database
    9. KRB5KDC_ERR_PRINCIPAL_NOT_UNIQUE: Principal has multiple entries in Kerberos database
    10. KRB5KDC_ERR_NULL_KEY: Client or server has a null key
    11. KRB5KDC_ERR_CANNOT_POSTDATE: Ticket is ineligible for postdating
    12. KRB5KDC_ERR_NEVER_VALID: Requested effective lifetime is negative or too short
    13. KRB5KDC_ERR_POLICY: KDC policy rejects request
    14. KRB5KDC_ERR_BADOPTION: KDC can't fulfill requested option
    15. KRB5KDC_ERR_ETYPE_NOSUPP: KDC has no support for encryption type
    16. KRB5KDC_ERR_SUMTYPE_NOSUPP: KDC has no support for checksum type
    17. KRB5KDC_ERR_PADATA_TYPE_NOSUPP: KDC has no support for padata type
    18. KRB5KDC_ERR_TRTYPE_NOSUPP: KDC has no support for transited type
    19. KRB5KDC_ERR_CLIENT_REVOKED: Clients credentials have been revoked
    20. KRB5KDC_ERR_SERVICE_REVOKED: Credentials for server have been revoked
    21. KRB5KDC_ERR_TGT_REVOKED: TGT has been revoked
    22. KRB5KDC_ERR_CLIENT_NOTYET: Client not yet valid - try again later
    23. KRB5KDC_ERR_SERVICE_NOTYET: Server not yet valid - try again later
    24. KRB5KDC_ERR_KEY_EXP: Password has expired
    25. KRB5KDC_ERR_PREAUTH_FAILED: Preauthentication failed
    26. KRB5KDC_ERR_PREAUTH_REQUIRED: Additional pre-auth@-en@-ti@-ca@-tion required
    27. KRB5KDC_ERR_SERVER_NOMATCH: Requested server and ticket don't match
    28. KRB5PLACEHOLD_27: KRB5 error code 27
    29. KRB5PLACEHOLD_28: KRB5 error code 28
    30. KRB5PLACEHOLD_29: KRB5 error code 29
    31. KRB5PLACEHOLD_30: KRB5 error code 30
    32. KRB5KRB_AP_ERR_BAD_INTEGRITY: Decrypt integrity check failed
    33. KRB5KRB_AP_ERR_TKT_EXPIRED: Ticket expired
    34. KRB5KRB_AP_ERR_TKT_NYV: Ticket not yet valid
    35. KRB5KRB_AP_ERR_REPEAT: Request is a replay
    36. KRB5KRB_AP_ERR_NOT_US: The ticket isn't for us
    37. KRB5KRB_AP_ERR_BADMATCH: Ticket/authenticator don't match
    38. KRB5KRB_AP_ERR_SKEW: Clock skew too great
    39. KRB5KRB_AP_ERR_BADADDR: Incorrect net address
    40. KRB5KRB_AP_ERR_BADVERSION: Protocol version mismatch
    41. KRB5KRB_AP_ERR_MSG_TYPE: Invalid message type
    42. KRB5KRB_AP_ERR_MODIFIED: Message stream modified
    43. KRB5KRB_AP_ERR_BADORDER: Message out of order
    44. KRB5KRB_AP_ERR_ILL_CR_TKT: Illegal cross-realm ticket
    45. KRB5KRB_AP_ERR_BADKEYVER: Key version is not available
    46. KRB5KRB_AP_ERR_NOKEY: Service key not available
    47. KRB5KRB_AP_ERR_MUT_FAIL: Mutual authentication failed
    48. KRB5KRB_AP_ERR_BADDIRECTION: Incorrect message direction
    49. KRB5KRB_AP_ERR_METHOD: Alternative authentication method required
    50. KRB5KRB_AP_ERR_BADSEQ: Incorrect sequence number in message
    51. KRB5KRB_AP_ERR_INAPP_CKSUM: Inappropriate type of checksum in message
    52. KRB5PLACEHOLD_51: KRB5 error code 51
    53. KRB5PLACEHOLD_52: KRB5 error code 52
    54. KRB5PLACEHOLD_53: KRB5 error code 53
    55. KRB5PLACEHOLD_54: KRB5 error code 54
    56. KRB5PLACEHOLD_55: KRB5 error code 55
    57. KRB5PLACEHOLD_56: KRB5 error code 56
    58. KRB5PLACEHOLD_57: KRB5 error code 57
    59. KRB5PLACEHOLD_58: KRB5 error code 58
    60. KRB5PLACEHOLD_59: KRB5 error code 59
    61. KRB5KRB_ERR_GENERIC: Generic error (see e-text)
    62. KRB5KRB_ERR_FIELD_TOOLONG: Field is too long for this implementation
    63. KRB5PLACEHOLD_62: KRB5 error code 62
    64. KRB5PLACEHOLD_63: KRB5 error code 63
    65. KRB5PLACEHOLD_64: KRB5 error code 64
    66. KRB5PLACEHOLD_65: KRB5 error code 65
    67. KRB5PLACEHOLD_66: KRB5 error code 66
    68. KRB5PLACEHOLD_67: KRB5 error code 67
    69. KRB5PLACEHOLD_68: KRB5 error code 68
    70. KRB5PLACEHOLD_69: KRB5 error code 69
    71. KRB5PLACEHOLD_70: KRB5 error code 70
    72. KRB5PLACEHOLD_71: KRB5 error code 71
    73. KRB5PLACEHOLD_72: KRB5 error code 72
    74. KRB5PLACEHOLD_73: KRB5 error code 73
    75. KRB5PLACEHOLD_74: KRB5 error code 74
    76. KRB5PLACEHOLD_75: KRB5 error code 75
    77. KRB5PLACEHOLD_76: KRB5 error code 76
    78. KRB5PLACEHOLD_77: KRB5 error code 77
    79. KRB5PLACEHOLD_78: KRB5 error code 78
    80. KRB5PLACEHOLD_79: KRB5 error code 79
    81. KRB5PLACEHOLD_80: KRB5 error code 80
    82. KRB5PLACEHOLD_81: KRB5 error code 81
    83. KRB5PLACEHOLD_82: KRB5 error code 82
    84. KRB5PLACEHOLD_83: KRB5 error code 83
    85. KRB5PLACEHOLD_84: KRB5 error code 84
    86. KRB5PLACEHOLD_85: KRB5 error code 85
    87. KRB5PLACEHOLD_86: KRB5 error code 86
    88. KRB5PLACEHOLD_87: KRB5 error code 87
    89. KRB5PLACEHOLD_88: KRB5 error code 88
    90. KRB5PLACEHOLD_89: KRB5 error code 89
    91. KRB5PLACEHOLD_90: KRB5 error code 90
    92. KRB5PLACEHOLD_91: KRB5 error code 91
    93. KRB5PLACEHOLD_92: KRB5 error code 92
    94. KRB5PLACEHOLD_93: KRB5 error code 93
    95. KRB5PLACEHOLD_94: KRB5 error code 94
    96. KRB5PLACEHOLD_95: KRB5 error code 95
    97. KRB5PLACEHOLD_96: KRB5 error code 96
    98. KRB5PLACEHOLD_97: KRB5 error code 97
    99. KRB5PLACEHOLD_98: KRB5 error code 98
    100. KRB5PLACEHOLD_99: KRB5 error code 99
    101. KRB5PLACEHOLD_100: KRB5 error code 100
    102. KRB5PLACEHOLD_101: KRB5 error code 101
    103. KRB5PLACEHOLD_102: KRB5 error code 102
    104. KRB5PLACEHOLD_103: KRB5 error code 103
    105. KRB5PLACEHOLD_104: KRB5 error code 104
    106. KRB5PLACEHOLD_105: KRB5 error code 105
    107. KRB5PLACEHOLD_106: KRB5 error code 106
    108. KRB5PLACEHOLD_107: KRB5 error code 107
    109. KRB5PLACEHOLD_108: KRB5 error code 108
    110. KRB5PLACEHOLD_109: KRB5 error code 109
    111. KRB5PLACEHOLD_110: KRB5 error code 110
    112. KRB5PLACEHOLD_111: KRB5 error code 111
    113. + KRB5PLACEHOLD_112: KRB5 error code 112
    114. KRB5PLACEHOLD_113: KRB5 error code 113
    115. KRB5PLACEHOLD_114: KRB5 error code 114
    116. KRB5PLACEHOLD_115: KRB5 error code 115
    117. KRB5PLACEHOLD_116: KRB5 error code 116
    118. KRB5PLACEHOLD_117: KRB5 error code 117
    119. KRB5PLACEHOLD_118: KRB5 error code 118
    120. KRB5PLACEHOLD_119: KRB5 error code 119
    121. KRB5PLACEHOLD_120: KRB5 error code 120
    122. KRB5PLACEHOLD_121: KRB5 error code 121
    123. KRB5PLACEHOLD_122: KRB5 error code 122
    124. KRB5PLACEHOLD_123: KRB5 error code 123
    125. KRB5PLACEHOLD_124: KRB5 error code 124
    126. KRB5PLACEHOLD_125: KRB5 error code 125
    127. KRB5PLACEHOLD_126: KRB5 error code 126
    128. KRB5PLACEHOLD_127: KRB5 error code 127
    129. KRB5_ERR_RCSID: $Id: admin.texinfo,v 1.2.2.4 1996/08/20 22:32:55 jcb Exp $
    130. KRB5_LIBOS_BADLOCKFLAG: Invalid flag for file lock mode
    131. KRB5_LIBOS_CANTREADPWD: Cannot read password
    132. KRB5_LIBOS_BADPWDMATCH: Password mismatch
    133. KRB5_LIBOS_PWDINTR: Password read interrupted
    134. KRB5_PARSE_ILLCHAR: Illegal character in component name
    135. KRB5_PARSE_MALFORMED: Malformed representation of principal
    136. KRB5_CONFIG_CANTOPEN: Can't open/find configuration file
    137. KRB5_CONFIG_BADFORMAT: Improper format of configuration file
    138. KRB5_CONFIG_NOTENUFSPACE: Insufficient space to return complete information
    139. KRB5_BADMSGTYPE: Invalid message type specified for encoding
    140. KRB5_CC_BADNAME: Credential cache name malformed
    141. KRB5_CC_UNKNOWN_TYPE: Unknown credential cache type
    142. KRB5_CC_NOTFOUND: Matching credential not found
    143. KRB5_CC_END: End of credential cache reached
    144. KRB5_NO_TKT_SUPPLIED: Request did not supply a ticket
    145. KRB5KRB_AP_WRONG_PRINC: Wrong principal in request
    146. KRB5KRB_AP_ERR_TKT_INVALID: Ticket has invalid flag set
    147. KRB5_PRINC_NOMATCH: Requested principal and ticket don't match
    148. KRB5_KDCREP_MODIFIED: KDC reply did not match expectations
    149. KRB5_KDCREP_SKEW: Clock skew too great in KDC reply
    150. KRB5_IN_TKT_REALM_MISMATCH: Client/server realm mismatch in initial ticket request
    151. KRB5_PROG_ETYPE_NOSUPP: Program lacks support for encryption type
    152. KRB5_PROG_KEYTYPE_NOSUPP: Program lacks support for key type
    153. KRB5_WRONG_ETYPE: Requested encryption type not used in message
    154. KRB5_PROG_SUMTYPE_NOSUPP: Program lacks support for checksum type
    155. KRB5_REALM_UNKNOWN: Cannot find KDC for requested realm
    156. KRB5_SERVICE_UNKNOWN: Kerberos service unknown
    157. KRB5_KDC_UNREACH: Cannot contact any KDC for requested realm
    158. KRB5_NO_LOCALNAME: No local name found for principal name
    159. KRB5_MUTUAL_FAILED: Mutual authentication failed
    160. KRB5_RC_TYPE_EXISTS: Replay cache type is already registered
    161. KRB5_RC_MALLOC: No more memory to allocate (in replay cache code)
    162. KRB5_RC_TYPE_NOTFOUND: Replay cache type is unknown
    163. KRB5_RC_UNKNOWN: Generic unknown RC error
    164. KRB5_RC_REPLAY: Message is a replay
    165. KRB5_RC_IO: Replay I/O operation failed XXX
    166. KRB5_RC_NOIO: Replay cache type does not support non-volatile storage
    167. KRB5_RC_PARSE: Replay cache name parse/format error
    168. KRB5_RC_IO_EOF: End-of-file on replay cache I/O
    169. KRB5_RC_IO_MALLOC: No more memory to allocate (in replay cache I/O code)
    170. KRB5_RC_IO_PERM: Permission denied in replay cache code
    171. KRB5_RC_IO_IO: I/O error in replay cache i/o code
    172. KRB5_RC_IO_UNKNOWN: Generic unknown RC/IO error
    173. KRB5_RC_IO_SPACE: Insufficient system space to store replay information
    174. KRB5_TRANS_CANTOPEN: Can't open/find realm translation file
    175. KRB5_TRANS_BADFORMAT: Improper format of realm translation file
    176. KRB5_LNAME_CANTOPEN: Can't open/find lname translation database
    177. KRB5_LNAME_NOTRANS: No translation available for requested principal
    178. KRB5_LNAME_BADFORMAT: Improper format of translation database entry
    179. KRB5_CRYPTO_INTERNAL: Cryptosystem internal error
    180. KRB5_KT_BADNAME: Key table name malformed
    181. KRB5_KT_UNKNOWN_TYPE: Unknown Key table type
    182. KRB5_KT_NOTFOUND: Key table entry not found
    183. KRB5_KT_END: End of key table reached
    184. KRB5_KT_NOWRITE: Cannot write to specified key table
    185. KRB5_KT_IOERR: Error writing to key table
    186. KRB5_NO_TKT_IN_RLM: Cannot find ticket for requested realm
    187. KRB5DES_BAD_KEYPAR: DES key has bad parity
    188. KRB5DES_WEAK_KEY: DES key is a weak key
    189. KRB5_BAD_ENCTYPE: Bad encryption type
    190. KRB5_BAD_KEYSIZE: Key size is incompatible with encryption type
    191. KRB5_BAD_MSIZE: Message size is incompatible with encryption type
    192. KRB5_CC_TYPE_EXISTS: Credentials cache type is already registered.
    193. KRB5_KT_TYPE_EXISTS: Key table type is already registered.
    194. KRB5_CC_IO: Credentials cache I/O operation failed XXX
    195. KRB5_FCC_PERM: Credentials cache file permissions incorrect
    196. KRB5_FCC_NOFILE: No credentials cache file found
    197. KRB5_FCC_INTERNAL: Internal file credentials cache error
    198. KRB5_CC_WRITE: Error writing to credentials cache file
    199. KRB5_CC_NOMEM: No more memory to allocate (in credentials cache code)
    200. KRB5_CC_FORMAT: Bad format in credentials cache
    201. KRB5_INVALID_FLAGS: Invalid KDC option combination (library internal error) [for dual tgt library calls]
    202. KRB5_NO_2ND_TKT: Request missing second ticket [for dual tgt library calls]
    203. KRB5_NOCREDS_SUPPLIED: No credentials supplied to library routine
    204. KRB5_SENDAUTH_BADAUTHVERS: Bad sendauth version was sent
    205. KRB5_SENDAUTH_BADAPPLVERS: Bad application version was sent (via sendauth)
    206. KRB5_SENDAUTH_BADRESPONSE: Bad response (during sendauth exchange)
    207. KRB5_SENDAUTH_REJECTED: Server rejected authentication (during sendauth exchange)
    208. KRB5_PREAUTH_BAD_TYPE: Unsupported preauthentication type
    209. KRB5_PREAUTH_NO_KEY: Required preauthentication key not supplied
    210. KRB5_PREAUTH_FAILED: Generic preauthentication failure
    211. KRB5_RCACHE_BADVNO: Unsupported replay cache format version number
    212. KRB5_CCACHE_BADVNO: Unsupported credentials cache format version number
    213. KRB5_KEYTAB_BADVNO: Unsupported key table format version number
    214. KRB5_PROG_ATYPE_NOSUPP: Program lacks support for address type
    215. KRB5_RC_REQUIRED: Message replay detection requires rcache parameter
    216. KRB5_ERR_BAD_HOSTNAME: Hostname cannot be canonicalized
    217. KRB5_ERR_HOST_REALM_UNKNOWN: Cannot determine realm for host
    218. KRB5_SNAME_UNSUPP_NAMETYPE: Conversion to service principal undefined for name type
    219. KRB5KRB_AP_ERR_V4_REPLY: Initial Ticket response appears to be Version 4 error
    220. KRB5_REALM_CANT_RESOLVE: Cannot resolve KDC for requested realm
    221. KRB5_TKT_NOT_FORWARDABLE: Requesting ticket can't get forwardable tickets
    222. KRB5_FWD_BAD_PRINCIPAL: Bad principal name while trying to forward credentials
    223. KRB5_GET_IN_TKT_LOOP: Looping detected inside krb5_get_in_tkt
    224. KRB5_CONFIG_NODEFREALM: Configuration file does not specify default realm
    225. KRB5_SAM_UNSUPPORTED: Bad SAM flags in obtain_sam_padata

    Kerberos V5 Database Library Error Codes

    This is the Kerberos v5 database library error code table.

    1. KRB5_KDB_RCSID: $Id: admin.texinfo,v 1.2.2.4 1996/08/20 22:32:55 jcb Exp $
    2. KRB5_KDB_INUSE: Entry already exists in database
    3. KRB5_KDB_UK_SERROR: Database store error
    4. KRB5_KDB_UK_RERROR: Database read error
    5. KRB5_KDB_UNAUTH: Insufficient access to perform requested operation
    6. KRB5_KDB_NOENTRY: No such entry in the database
    7. KRB5_KDB_ILL_WILDCARD: Illegal use of wildcard
    8. KRB5_KDB_DB_INUSE: Database is locked or in use--try again later
    9. KRB5_KDB_DB_CHANGED: Database was modified during read
    10. KRB5_KDB_TRUNCATED_RECORD: Database record is incomplete or corrupted
    11. KRB5_KDB_RECURSIVELOCK: Attempt to lock database twice
    12. KRB5_KDB_NOTLOCKED: Attempt to unlock database when not locked
    13. KRB5_KDB_BADLOCKMODE: Invalid kdb lock mode
    14. KRB5_KDB_DBNOTINITED: Database has not been initialized
    15. KRB5_KDB_DBINITED: Database has already been initialized
    16. KRB5_KDB_ILLDIRECTION: Bad direction for converting keys
    17. KRB5_KDB_NOMASTERKEY: Cannot find master key record in database
    18. KRB5_KDB_BADMASTERKEY: Master key does not match database
    19. KRB5_KDB_INVALIDKEYSIZE: Key size in database is invalid
    20. KRB5_KDB_CANTREAD_STORED: Cannot find/read stored master key
    21. KRB5_KDB_BADSTORED_MKEY: Stored master key is corrupted
    22. KRB5_KDB_CANTLOCK_DB: Insufficient access to lock database
    23. KRB5_KDB_DB_CORRUPT: Database format error
    24. KRB5_KDB_BAD_VERSION: Unsupported version in database entry
    25. KRB5_KDB_BAD_SALTTYPE: Unsupported salt type
    26. KRB5_KDB_BAD_ENCTYPE: Unsupported encryption type

    Kerberos V5 Magic Numbers Error Codes

    This is the Kerberos v5 magic numbers error code table.

    1. KV5M_NONE: Kerberos V5 magic number table
    2. KV5M_PRINCIPAL: Bad magic number for krb5_principal structure
    3. KV5M_DATA: Bad magic number for krb5_data structure
    4. KV5M_KEYBLOCK: Bad magic number for krb5_keyblock structure
    5. KV5M_CHECKSUM: Bad magic number for krb5_checksum structure
    6. KV5M_ENCRYPT_BLOCK: Bad magic number for krb5_encrypt_block structure
    7. KV5M_ENC_DATA: Bad magic number for krb5_enc_data structure
    8. KV5M_CRYPTOSYSTEM_ENTRY: Bad magic number for krb5_cryp@-to@-sys@-tem_entry structure
    9. KV5M_CS_TABLE_ENTRY: Bad magic number for krb5_cs_table_entry structure
    10. KV5M_CHECKSUM_ENTRY: Bad magic number for krb5_check@-sum_en@-try structure
    11. KV5M_AUTHDATA: Bad magic number for krb5_authdata structure
    12. KV5M_TRANSITED: Bad magic number for krb5_transited structure
    13. KV5M_ENC_TKT_PART: Bad magic number for krb5_enc_tkt_part structure
    14. KV5M_TICKET: Bad magic number for krb5_ticket structure
    15. KV5M_AUTHENTICATOR: Bad magic number for krb5_authenticator structure
    16. KV5M_TKT_AUTHENT: Bad magic number for krb5_tkt_authent structure
    17. KV5M_CREDS: Bad magic number for krb5_creds structure
    18. KV5M_LAST_REQ_ENTRY: Bad magic number for krb5_last_req_entry structure
    19. KV5M_PA_DATA: Bad magic number for krb5_pa_data structure
    20. KV5M_KDC_REQ: Bad magic number for krb5_kdc_req structure
    21. KV5M_ENC_KDC_REP_PART: Bad magic number for
      krb5_enc_kdc_rep_part structure
    22. KV5M_KDC_REP: Bad magic number for krb5_kdc_rep structure
    23. KV5M_ERROR: Bad magic number for krb5_error structure
    24. KV5M_AP_REQ: Bad magic number for krb5_ap_req structure
    25. KV5M_AP_REP: Bad magic number for krb5_ap_rep structure
    26. KV5M_AP_REP_ENC_PART: Bad magic number for
      krb5_ap_rep_enc_part structure
    27. KV5M_RESPONSE: Bad magic number for krb5_response structure
    28. KV5M_SAFE: Bad magic number for krb5_safe structure
    29. KV5M_PRIV: Bad magic number for krb5_priv structure
    30. KV5M_PRIV_ENC_PART: Bad magic number for krb5_priv_enc_part structure
    31. KV5M_CRED: Bad magic number for krb5_cred structure
    32. KV5M_CRED_INFO: Bad magic number for krb5_cred_info structure
    33. KV5M_CRED_ENC_PART: Bad magic number for krb5_cred_enc_part structure
    34. KV5M_PWD_DATA: Bad magic number for krb5_pwd_data structure
    35. KV5M_ADDRESS: Bad magic number for krb5_address structure
    36. KV5M_KEYTAB_ENTRY: Bad magic number for krb5_keytab_entry structure
    37. KV5M_CONTEXT: Bad magic number for krb5_context structure
    38. KV5M_OS_CONTEXT: Bad magic number for krb5_os_context structure
    39. KV5M_ALT_METHOD: Bad magic number for krb5_alt_method structure
    40. KV5M_ETYPE_INFO_ENTRY: Bad magic number for
      krb5_etype_info_entry structure
    41. KV5M_DB_CONTEXT: Bad magic number for krb5_db_context structure
    42. KV5M_AUTH_CONTEXT: Bad magic number for krb5_auth_context structure
    43. KV5M_KEYTAB: Bad magic number for krb5_keytab structure
    44. KV5M_RCACHE: Bad magic number for krb5_rcache structure
    45. KV5M_CCACHE: Bad magic number for krb5_ccache structure
    46. KV5M_PREAUTH_OPS: Bad magic number for krb5_preauth_ops
    47. KV5M_SAM_CHALLENGE: Bad magic number for krb5_sam_challenge
    48. KV5M_SAM_KEY: Bad magic number for krb5_sam_key
    49. KV5M_ENC_SAM_RESPONSE_ENC: Bad magic number for
      krb5_enc_sam_response_enc
    50. KV5M_SAM_RESPONSE: Bad magic number for krb5_sam_response
    51. KV5M_PREDICTED_SAM_RESPONSE: Bad magic number for krb5_predicted_sam_response
    52. KV5M_PASSWD_PHRASE_ELEMENT: Bad magic number for passwd_phrase_element

    ASN.1 Error Codes

    1. ASN1_BAD_TIMEFORMAT: ASN.1 failed call to system time library
    2. ASN1_MISSING_FIELD: ASN.1 structure is missing a required field
    3. ASN1_MISPLACED_FIELD: ASN.1 unexpected field number
    4. ASN1_TYPE_MISMATCH: ASN.1 type numbers are inconsistent
    5. ASN1_OVERFLOW: ASN.1 value too large
    6. ASN1_OVERRUN: ASN.1 encoding ended unexpectedly
    7. ASN1_BAD_ID: ASN.1 identifier doesn't match expected value
    8. ASN1_BAD_LENGTH: ASN.1 length doesn't match expected value
    9. ASN1_BAD_FORMAT: ASN.1 badly-formatted encoding
    10. ASN1_PARSE_ERROR: ASN.1 parse error

    GSSAPI Error Codes

    Generic GSSAPI Errors:

    1. G_BAD_SERVICE_NAME: No in SERVICE-NAME name string
    2. G_BAD_STRING_UID: STRING-UID-NAME contains nondigits
    3. G_NOUSER: UID does not resolve to username
    4. G_VALIDATE_FAILED: Validation error
    5. G_BUFFER_ALLOC: Couldn't allocate gss_buffer_t data
    6. G_BAD_MSG_CTX: Message context invalid
    7. G_WRONG_SIZE: Buffer is the wrong size
    8. G_BAD_USAGE: Credential usage type is unknown
    9. G_UNKNOWN_QOP: Unknown quality of protection specified
    10. G_BAD_HOSTNAME: Hostname in SERVICE-NAME string could not be canonicalized

    Kerberos 5 GSSAPI Errors:

    1. KG_CCACHE_NOMATCH: Principal in credential cache does not match desired name
    2. KG_KEYTAB_NOMATCH: No principal in keytab matches desired name
    3. KG_TGT_MISSING: Credential cache has no TGT
    4. KG_NO_SUBKEY: Authenticator has no subkey
    5. KG_CONTEXT_ESTABLISHED: Context is already fully established
    6. KG_BAD_SIGN_TYPE: Unknown signature type in token
    7. KG_BAD_LENGTH: Invalid field length in token
    8. KG_CTX_INCOMPLETE: Attempt to use incomplete security context
    9. KG_CONTEXT: Bad magic number for krb5_gss_ctx_id_t
    10. KG_CRED: Bad magic number for krb5_gss_cred_id_t
    11. KG_ENC_DESC: Bad magic number for krb5_gss_enc_desc

    kadmin Time Zones

    This is a complete listing of the time zones recognized by the kadmin command.

    gmt
    Greenwich Mean Time
    ut, utc
    Universal Time (Coordinated).
    wet
    Western European Time. (Same as GMT.)
    bst
    British Summer Time. (1 hour ahead of GMT.)
    wat
    West Africa Time. (1 hour behind GMT.)
    at
    Azores Time. (2 hours behind GMT.)
    bst
    Brazil Standard Time. (3 hours behind GMT.) Note that the abbreviation BST also stands for British Summer Time.
    gst
    Greenland Standard Time. (3 hours behind GMT.) Note that the abbreviation GST also stands for Guam Standard Time.
    nft
    Newfoundland Time. (3.5 hours behind GMT.)
    nst
    Newfoundland Standard Time. (3.5 hours behind GMT.)
    ndt
    Newfoundland Daylight Time. (2.5 hours behind GMT.)
    ast
    Atlantic Standard Time. (4 hours behind GMT.)
    adt
    Atlantic Daylight Time. (3 hours behind GMT.)
    est
    Eastern Standard Time. (5 hours behind GMT.)
    edt
    Eastern Daylight Time. (4 hours behind GMT.)
    cst
    Central Standard Time. (6 hours behind GMT.)
    cdt
    Central Daylight Time. (5 hours behind GMT.)
    mst
    Mountain Standard Time. (7 hours behind GMT.)
    mdt
    Mountain Daylight Time. (6 hours behind GMT.)
    pst
    Pacific Standard Time. (8 hours behind GMT.)
    pdt
    Pacific Daylight Time. (7 hours behind GMT.)
    yst
    Yukon Standard Time. (9 hours behind GMT.)
    ydt
    Yukon Daylight Time. (8 hours behind GMT.)
    hst
    Hawaii Standard Time. (10 hours behind GMT.)
    hdt
    Hawaii Daylight Time. (9 hours behind GMT.)
    cat
    Central Alaska Time. (10 hours behind GMT.)
    ahst
    Alaska-Hawaii Standard Time. (10 hours behind GMT.)
    nt
    Nome Time. (11 hours behind GMT.)
    idlw
    International Date Line West Time. (12 hours behind GMT.)
    cet
    Central European Time. (1 hour ahead of GMT.)
    met
    Middle European Time. (1 hour ahead of GMT.)
    mewt
    Middle European Winter Time. (1 hour ahead of GMT.)
    mest
    Middle European Summer Time. (2 hours ahead of GMT.)
    swt
    Swedish Winter Time. (1 hour ahead of GMT.)
    sst
    Swedish Summer Time. (1 hours ahead of GMT.)
    fwt
    French Winter Time. (1 hour ahead of GMT.)
    fst
    French Summer Time. (2 hours ahead of GMT.)
    eet
    Eastern Europe Time; Russia Zone 1. (2 hours ahead of GMT.)
    bt
    Baghdad Time; Russia Zone 2. (3 hours ahead of GMT.)
    it
    Iran Time. (3.5 hours ahead of GMT.)
    zp4
    Russia Zone 3. (4 hours ahead of GMT.)
    zp5
    Russia Zone 4. (5 hours ahead of GMT.)
    ist
    Indian Standard Time. (5.5 hours ahead of GMT.)
    zp6
    Russia Zone 5. (6 hours ahead of GMT.)
    nst
    North Sumatra Time. (6.5 hours ahead of GMT.) Note that the abbreviation NST is also used for Newfoundland Stanard Time.
    sst
    South Sumatra Time; Russia Zone 6. (7 hours ahead of GMT.) Note that SST is also Swedish Summer Time.
    wast
    West Australian Standard Time. (7 hours ahead of GMT.)
    wadt
    West Australian Daylight Time. (8 hours ahead of GMT.)
    jt
    Java Time. (7.5 hours ahead of GMT.)
    cct
    China Coast Time; Russia Zone 7. (8 hours ahead of GMT.)
    jst
    Japan Standard time; Russia Zone 8. (9 hours ahead of GMT.)
    kst
    Korean Standard Time. (9 hours ahead of GMT.)
    cast
    Central Australian Standard Time. (9.5 hours ahead of GMT.)
    cadt
    Central Australian Daylight Time. (10.5 hours ahead of GMT.)
    east
    Eastern Australian Standard Time. (10 hours ahead of GMT.)
    eadt
    Eastern Australian Daylight Time. (11 hours ahead of GMT.)
    gst
    Guam Standard Time; Russia Zone 9. (10 hours ahead of GMT.)
    kdt
    Korean Daylight Time. (10 hours ahead of GMT.)
    nzt
    New Zealand Time. (12 hours ahead of GMT.)
    nzst
    New Zealand Standard Time. (12 hours ahead of GMT.)
    nzdt
    New Zealand Daylight Time. (13 hours ahead of GMT.)
    idle
    International Date Line East. (12 hours ahead of GMT.)