1KDC(8) BSD System Manager's Manual KDC(8)
2
4 kdc — Kerberos 5 server
5
7 kdc [-c file | --config-file=file] [-p | --no-require-preauth]
8 [--max-request=size] [-H | --enable-http] [-r string |
9 --v4-realm=string] [-P portspec | --ports=portspec] [--detach]
10 [--disable-des] [--addresses=list of addresses]
11
13 kdc serves requests for tickets. When it starts, it first checks the
14 flags passed, any options that are not specified with a command line flag
15 are taken from a config file, or from a default compiled-in value.
16 Options supported:
18 -c file, --config-file=file
20 Specifies the location of the config file, the default is
21 /var/heimdal/kdc.conf. This is the only value that can't be
22 specified in the config file.
23 -p, --no-require-preauth
25 Turn off the requirement for pre-autentication in the initial AS-
26 REQ for all principals. The use of pre-authentication makes it
27 more difficult to do offline password attacks. You might want to
28 turn it off if you have clients that don't support pre-authenti‐
29 cation. Since the version 4 protocol doesn't support any pre-
30 authentication, serving version 4 clients is just about the same
31 as not requiring pre-athentication. The default is to require
32 pre-authentication. Adding the require-preauth per principal is
33 a more flexible way of handling this.
34 --max-request=size
36 Gives an upper limit on the size of the requests that the kdc is
37 willing to handle.
38 -H, --enable-http
40 Makes the kdc listen on port 80 and handle requests encapsulated
41 in HTTP.
42 -r string, --v4-realm=string
44 What realm this server should act as when dealing with version 4
45 requests. The database can contain any number of realms, but
46 since the version 4 protocol doesn't contain a realm for the
47 server, it must be explicitly specified. The default is whatever
48 is returned by krb_get_lrealm(). This option is only available
49 if the KDC has been compiled with version 4 support.
50 -P portspec, --ports=portspec
52 Specifies the set of ports the KDC should listen on. It is given
53 as a white-space separated list of services or port numbers.
54 --addresses=list of addresses
56 The list of addresses to listen for requests on. By default, the
57 kdc will listen on all the locally configured addresses. If only
58 a subset is desired, or the automatic detection fails, this
59 option might be used.
60 --detach
62 detach from pty and run as a daemon.
63 --disable-des
65 disable all des encryption types, makes the kdc not use them.
66 All activities are logged to one or more destinations, see krb5.conf(5),
68 and krb5_openlog(3). The entity used for logging is kdc.
69
71 The configuration file has the same syntax as krb5.conf(5), but will be
72 read before /etc/krb5.conf, so it may override settings found there.
73 Options specific to the KDC only are found in the “[kdc]” section. All
74 the command-line options can preferably be added in the configuration
75 file. The only difference is the pre-authentication flag, which has to
76 be specified as:
77 require-preauth = no
79 (in fact you can specify the option as --require-preauth=no).
81 And there are some configuration options which do not have command-line
83 equivalents:
84 enable-digest = boolean
86 turn on support for digest processing in the KDC. The default
87 is FALSE.
88 check-ticket-addresses = boolean
90 Check the addresses in the ticket when processing TGS
91 requests. The default is TRUE.
92 allow-null-ticket-addresses = boolean
94 Permit tickets with no addresses. This option is only rele‐
95 vant when check-ticket-addresses is TRUE.
96 allow-anonymous = boolean
98 Permit anonymous tickets with no addresses.
99 max-kdc-datagram-reply-length = number
101 Maximum packet size the UDP rely that the KDC will transmit,
102 instead the KDC sends back a reply telling the client to use
103 TCP instead.
104 transited-policy = always-check | allow-per-principal |
106 always-honour-request
107 This controls how KDC requests with the
108 disable-transited-check flag are handled. It can be one of:
109 always-check
111 Always check transited encoding, this is the
112 default.
113 allow-per-principal
115 Currently this is identical to always-check. In a
116 future release, it will be possible to mark a prin‐
117 cipal as able to handle unchecked requests.
118 always-honour-request
120 Always do what the client asked. In a future
121 release, it will be possible to force a check per
122 principal.
123 encode_as_rep_as_tgs_rep = boolean
125 Encode AS-Rep as TGS-Rep to be bug-compatible with old DCE
126 code. The Heimdal clients allow both.
127 kdc_warn_pwexpire = time
129 How long before password/principal expiration the KDC should
130 start sending out warning messages.
131 The configuration file is only read when the kdc is started. If changes
133 made to the configuration file are to take effect, the kdc needs to be
134 restarted.
135 An example of a config file:
137 [kdc]
139 require-preauth = no
140 v4-realm = FOO.SE
141
143 If the machine running the KDC has new addresses added to it, the KDC
144 will have to be restarted to listen to them. The reason it doesn't just
145 listen to wildcarded (like INADDR_ANY) addresses, is that the replies has
146 to come from the same address they were sent to, and most OS:es doesn't
147 pass this information to the application. If your normal mode of opera‐
148 tion require that you add and remove addresses, the best option is proba‐
149 bly to listen to a wildcarded TCP socket, and make sure your clients use
150 TCP to connect. For instance, this will listen to IPv4 TCP port 88 only:
151 kdc --addresses=0.0.0.0 --ports="88/tcp"
153 There should be a way to specify protocol, port, and address triplets,
155 not just addresses and protocol, port tuples.
156
158 kinit(1), krb5.conf(5)
159HEIMDAL August 24, 2006 HEIMDAL