OpenBSD manual page server

Manual Page Search Parameters

KRB5.CONF(5) File Formats Manual KRB5.CONF(5)

krb5.confconfiguration file for Kerberos 5

#include <krb5.h>

The krb5.conf file specifies several configuration parameters for the Kerberos 5 library, as well as for some programs.

The file consists of one or more sections, containing a number of bindings. The value of each binding can be either a string or a list of other bindings. The grammar looks like:

	/* empty */

	section sections

	'[' section_name ']' bindings


	binding bindings

	name '=' STRING
	name '=' '{' bindings '}'


STRINGs consists of one or more non-whitespace characters.

STRINGs that are specified later in this man-page uses the following notation.

values can be either yes/true or no/false.
values can be a list of year, month, day, hour, min, second. Example: 1 month 2 days 30 min. If no unit is given, seconds is assumed.
valid encryption types are: des-cbc-crc, des-cbc-md4, des-cbc-md5, des3-cbc-sha1, arcfour-hmac-md5, aes128-cts-hmac-sha1-96, and aes256-cts-hmac-sha1-96 .
an address can be either a IPv4 or a IPv6 address.

Currently recognised sections and bindings are:

Specifies the default values to be used for Kerberos applications. You can specify defaults per application, realm, or a combination of these. The preference order is:
  1. application realm option
  2. application option
  3. realm option
  4. option

The supported options are:

When obtaining initial credentials, make the credentials forwardable.
When obtaining initial credentials, make the credentials proxiable.
When obtaining initial credentials, request them for an empty set of addresses, making the tickets valid from any address.
Default ticket lifetime.
Default renewable ticket lifetime.
Use encryption, when available.
Forward credentials to remote host (for rsh(1), telnet(1), etc).
Default realm to use, this is also known as your “local realm”. The default is the result of (local hostname).
Maximum time differential (in seconds) allowed when comparing times. Default is 300 seconds (five minutes).
Maximum time to wait for a reply from the kdc, default is 3 seconds.
These are described in the krb5_425_conv_principal(3) manual page.
destination-realm = next-hop-realm
This is deprecated, see the capaths section below.
the default credentials cache name. The string can contain variables that are expanded on runtime. Only support variable now is %{uid} that expands to the current user id.
etypes ...
A list of default encryption types to use.
etypes ...
A list of default encryption types to use when requesting a DES credential.
The keytab to use if no other is specified, default is “FILE:/etc/kerberosV/krb5.keytab”.
Use DNS SRV records to lookup KDC services location.
Use DNS TXT records to lookup domain to realm mappings.
Try to keep track of the time differential between the local machine and the KDC, and then compensate for that when issuing requests.
The max number of times to try to contact each KDC.
The threshold where protocols with tiny maximum message sizes are not considered usable to send messages to the KDC.
Default ticket lifetime.
Default renewable ticket lifetime.
When obtaining initial credentials, make the credentials forwardable. This option is also valid in the [realms] section.
When obtaining initial credentials, make the credentials proxiable. This option is also valid in the [realms] section.
If enabled, failure to verify credentials against a local key is a fatal error. The application has to be able to read the corresponding service key for this to work. Some applications, like su(1), enable this option unconditionally.
How soon to warn for expiring password. Default is seven days.
A HTTP-proxy to use when talking to the KDC via HTTP.
Enable using DNS via HTTP.
address ...
A list of addresses to get tickets for along with all local addresses.
How to print time strings in logs, this string is passed to strftime(3).
How to print date strings in logs, this string is passed to strftime(3).
Write log-entries using UTC instead of your local time zone.
Scan all network interfaces for addresses, as opposed to simply using the address associated with the system's host name.
Use file credential cache format version specified.
Also get Kerberos 4 tickets in kinit, login, and other programs. This option is also valid in the [realms] section.
Use MIT compatible format for file credential cache. It's the field ticketflags that is stored in reverse bit order for older than Heimdal 0.7. Setting this flag to TRUE make it store the MIT way, this is default for Heimdal 0.7.
This is a list of mappings from DNS domain to Kerberos realm. Each binding in this section looks like:

domain = realm

The domain can be either a full name of a host or a trailing component, in the latter case the domain-string should start with a period. The trailing component only matches hosts that are in the same domain, ie “” matches “”, but not “”.

The realm may be the token `dns_locate', in which case the actual realm will be determined using DNS (independently of the setting of the `dns_lookup_realm' option).

Specifies a list of kdcs for this realm. If the optional port is absent, the default value for the “kerberos/udp” “kerberos/tcp”, and “http/tcp” port (depending on service) will be used. The kdcs will be used in the order that they are specified.

The optional service specifies over what medium the kdc should be contacted. Possible services are “udp”, “tcp”, and “http”. Http can also be written as “http://”. Default service is “udp” and “tcp”.

Specifies the admin server for this realm, where all the modifications to the database are performed.
Points to the server where all the password changes are performed. If there is no such entry, the kpasswd port on the admin_server host will be tried.
Points to the server that does 524 conversions. If it is not mentioned, the krb524 port on the kdcs will be tried.
See krb5_425_conv_principal(3).
a boolan variable that defaults to false. Old DCE secd (pre 1.1) might need this to be true.
client-realm = {
server-realm = hop-realm ...
This serves two purposes. First the first listed hop-realm tells a client which realm it should contact in order to ultimately obtain credentials for a service in the server-realm. Secondly, it tells the KDC (and other servers) which realms are allowed in a multi-hop traversal from client-realm to server-realm. Except for the client case, the order of the realms are not important.
entity = destination
Specifies that entity should use the specified destination for logging. See the krb5_openlog(3) manual page for a list of defined destinations.
= {
Use this database for this realm. See the info documetation how to configure diffrent database backends.
Specifies the realm that will be stored in this database. It realm isn't set, it will used as the default database, there can only be one entry that doesn't have a realm stanza.
Use this keytab file for the master key of this database. If not specified DATABASENAME.mkey will be used.
Use this file for the ACL list of this database.
Use this file as the log of changes performed to the database. This file is used by ipropd-master for propagating changes to slaves.
Maximum size of a kdc request.
If set pre-authentication is required. Since krb4 requests are not pre-authenticated they will be rejected.
list of ports
List of ports the kdc should listen to.
list of interfaces
List of addresses the kdc should bind to.
Turn on Kerberos 4 support.
To what realm v4 requests should be mapped.
Should the Kerberos 524 converting facility be turned on. Default is the same as enable-kerberos4.
Should the kdc answer kdc-requests over http.
If this kdc should emulate the AFS kaserver.
Verify the addresses in the tickets used in tgs requests.
Allow address-less tickets.
If the kdc is allowed to hand out anonymous tickets.
Encode as-rep as tgs-rep tobe compatible with mistakes older DCE secd did.
The time before expiration that the user should be warned that her password is about to expire.
What type of logging the kdc should use, see also [logging]/kdc.
principal = BOOL
boolean value if the 524 daemon should return AFS 2b tokens for principal.
structural object
If the LDAP backend is used for storing principals, this is the structural object that will be used when creating and when reading objects. The default value is account .
creation dn
is the dn that will be appended to the principal when creating entries. Default value is the search dn.
If pre-authentication is required to talk to the kadmin server.
If a principal already have its password set for expiration, this is the time it will be valid for after a change.
For each entry in default_keys try to parse it as a sequence of etype:salttype:salt syntax of this if something like:


If etype is omitted it means everything, and if string is omitted it means the default salt string (for that principal and encryption type). Additional special values of keytypes are:

The Kerberos 5 salt pw-salt
The Kerberos 4 salt des:pw-salt:
When true, this is the same as

default_keys = des3:pw-salt v4

and is only left for backwards compatibility.

KRB5_CONFIG points to the configuration file to read.

configuration file for Kerberos 5.

	default_realm = FOO.SE
[domain_realm] = FOO.SE = FOO.SE
	FOO.SE = {
		kdc =
		v4_name_convert = {
			rcmd = host
		v4_instance_convert = {
			xyz =
		default_domain =
	kdc = FILE:/var/heimdal/kdc.log

Since krb5.conf is read and parsed by the krb5 library, there is not a lot of opportunities for programs to report parsing errors in any useful format. To help overcome this problem, there is a program verify_krb5_conf that reads krb5.conf and tries to emit useful diagnostics from parsing errors. Note that this program does not have any way of knowing what options are actually used and thus cannot warn about unknown or misspelled ones.

kinit(1), krb5_425_conv_principal(3), krb5_openlog(3), strftime(3), verify_krb5_conf(8)

May 4, 2005 HEIMDAL