
KDC(8)                   UNIX System Manager's Manual                   KDC(8)

NNAAMMEE
     kkddcc - Kerberos 5 server

SSYYNNOOPPSSIISS
     kkddcc [--cc _f_i_l_e | ----ccoonnffiigg--ffiillee==_f_i_l_e] [--pp | ----nnoo--rreeqquuiirree--pprreeaauutthh]
     [----mmaaxx--rreeqquueesstt==_s_i_z_e] [--HH | ----eennaabbllee--hhttttpp] [----nnoo--552244] [----kkeerrbbeerrooss44]
     [----kkeerrbbeerrooss44--ccrroossss--rreeaallmm] [--rr _s_t_r_i_n_g | ----vv44--rreeaallmm==_s_t_r_i_n_g]
     [--KK | ----kkaasseerrvveerr] [--PP _p_o_r_t_s_p_e_c | ----ppoorrttss==_p_o_r_t_s_p_e_c] [----ddeettaacchh]
     [----ddiissaabbllee--DDEESS] [----aaddddrreesssseess==_l_i_s_t _o_f _a_d_d_r_e_s_s_e_s]

DDEESSCCRRIIPPTTIIOONN
     kkddcc serves requests for tickets.  When it starts, it first checks the
     flags passed, any options that are not specified with a command line flag
     are taken from a config file, or from a default compiled-in value.

     Options supported:

     --cc _f_i_l_e, ----ccoonnffiigg--ffiillee==_f_i_l_e
             Specifies the location of the config file, the default is
             _/_v_a_r_/_h_e_i_m_d_a_l_/_k_d_c_._c_o_n_f. This is the only value that can't be spec-
             ified in the config file.

     --pp, ----nnoo--rreeqquuiirree--pprreeaauutthh
             Turn off the requirement for pre-autentication in the initial AS-
             REQ for all principals.  The use of pre-authentication makes it
             more difficult to do offline password attacks.  You might want to
             turn it off if you have clients that don't support pre-authenti-
             cation.  Since the version 4 protocol doesn't support any pre-au-
             thentication, serving version 4 clients is just about the same as
             not requiring pre-athentication.  The default is to require pre-
             authentication.  Adding the require-preauth per principal is a
             more flexible way of handling this.

     ----mmaaxx--rreeqquueesstt==_s_i_z_e
             Gives an upper limit on the size of the requests that the kdc is
             willing to handle.

     --HH, ----eennaabbllee--hhttttpp
             Makes the kdc listen on port 80 and handle requests encapsulated
             in HTTP.

     ----nnoo--552244
             don't respond to 524 requests

     ----kkeerrbbeerrooss44
             respond to Kerberos 4 requests

     ----kkeerrbbeerrooss44--ccrroossss--rreeaallmm
             respond to Kerberos 4 requests from foreign realms.  This is a
             known security hole and should not be enabled unless you under-
             stand the consequences and are willing to live with them.

     --rr _s_t_r_i_n_g, ----vv44--rreeaallmm==_s_t_r_i_n_g
             What realm this server should act as when dealing with version 4
             requests.  The database can contain any number of realms, but
             since the version 4 protocol doesn't contain a realm for the
             server, it must be explicitly specified.  The default is whatever
             is returned by kkrrbb__ggeett__llrreeaallmm().  This option is only availabe if
             the KDC has been compiled with version 4 support.

     --KK, ----kkaasseerrvveerr

             Enable kaserver emulation (in case it's compiled in).

     --PP _p_o_r_t_s_p_e_c, ----ppoorrttss==_p_o_r_t_s_p_e_c
             Specifies the set of ports the KDC should listen on.  It is given
             as a white-space separated list of services or port numbers.

     ----aaddddrreesssseess==_l_i_s_t _o_f _a_d_d_r_e_s_s_e_s
             The list of addresses to listen for requests on.  By default, the
             kdc will listen on all the locally configured addresses.  If only
             a subset is desired, or the automatic detection fails, this op-
             tion might be used.

     ----ddeettaacchh
             detach from pty and run as a daemon.

     ----ddiissaabbllee--DDEESS
             disable add des encryption types, makes the kdc not use them.

     All activities are logged to one or more destinations, see krb5.conf(5),
     and krb5_openlog(3).  The entity used for logging is kkddcc.

CCOONNFFIIGGUURRAATTIIOONN FFIILLEE
     The configuration file has the same syntax as krb5.conf(5),  but will be
     read before _/_e_t_c_/_k_r_b_5_._c_o_n_f, so it may override settings found there.  Op-
     tions specific to the KDC only are found in the ``[kdc]'' section.  All
     the command-line options can preferably be added in the configuration
     file.  The only difference is the pre-authentication flag, which has to
     be specified as:

           require-preauth = no

     (in fact you can specify the option as ----rreeqquuiirree--pprreeaauutthh==nnoo).

     And there are some configuration options which do not have command-line
     equivalents:

           check-ticket-addresses = _b_o_o_l_e_a_n
                Check the addresses in the ticket when processing TGS re-
                quests.  The default is TRUE.

           allow-null-ticket-addresses = _b_o_o_l_e_a_n
                Permit tickets with no addresses.  This option is only rele-
                vant when check-ticket-addresses is TRUE.

           allow-anonymous = _b_o_o_l_e_a_n
                Permit anonymous tickets with no addresses.

           transited-policy = always-check | allow-per-principal | always-hon-
                our-request
                This controls how KDC requests with the disable-transited-
                check flag are handled. It can be one of:

                      always-check
                           Always check transited encoding, this is the de-
                           fault.

                      allow-per-principal
                           Currently this is identical to always-check. In a
                           future release, it will be possible to mark a prin-
                           cipal as able to handle unchecked requests.

                      always-honour-request
                           Always do what the client asked.  In a future re-
                           lease, it will be possible to force a check per
                           principal.


           encode_as_rep_as_tgs_rep = _b_o_o_l_e_a_n
                Encode AS-Rep as TGS-Rep to be bug-compatible with old DCE
                code.  The Heimdal clients allow both.

           kdc_warn_pwexpire = _t_i_m_e
                How long before password/principal expiration the KDC should
                start sending out warning messages.

     The configuration file is only read when the kkddcc is started.  If changes
     made to the configuration file are to take effect, the kkddcc needs to be
     restarted.

     An example of a config file:

           [kdc]
                   require-preauth = no
                   v4-realm = FOO.SE

BBUUGGSS
     If the machine running the KDC has new addresses added to it, the KDC
     will have to be restarted to listen to them.  The reason it doesn't just
     listen to wildcarded (like INADDR_ANY) addresses, is that the replies has
     to come from the same address they were sent to, and most OS:es doesn't
     pass this information to the application.  If your normal mode of opera-
     tion require that you add and remove addresses, the best option is proba-
     bly to listen to a wildcarded TCP socket, and make sure your clients use
     TCP to connect.  For instance, this will listen to IPv4 TCP port 88 only:

           kdc --addresses=0.0.0.0 --ports="88/tcp"

     There should be a way to specify protocol, port, and address triplets,
     not just addresses and protocol, port tuples.

SSEEEE AALLSSOO
     kinit(1),  krb5.conf(5)

 HEIMDAL                       December 17, 2004                             3
