oysteikt/heimdal
0
0
Fork 0
Code Issues 5 Pull Requests Releases Activity

add blurb about adding and removing addresses; update kdc.conf section

Browse Source 
to match reality


git-svn-id: svn://svn.h5l.se/heimdal/trunk/heimdal@11196 ec53bebd-3082-4978-b11e-865c3cabbd6b
This commit is contained in:
Johan Danielsson
2002-08-22 09:55:00 +00:00
parent 98590bf680
commit f781cef162
1 changed files with 26 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

35
kdc/kdc.8
View File

@@ -1,6 +1,6 @@
.\" $Id$ .\" $Id$
.\" .\"
.Dd July 27, 1997 .Dd August 22, 2002
.Dt KDC 8 .Dt KDC 8
.Os HEIMDAL .Os HEIMDAL
.Sh NAME .Sh NAME
@@ -96,14 +96,14 @@ and
The entity used for logging is The entity used for logging is
.Nm kdc . .Nm kdc .
.Sh CONFIGURATION FILE .Sh CONFIGURATION FILE
The configuration file has the same syntax as the The configuration file has the same syntax as
.Pa krb5.conf .Xr krb5.conf 5 ,
file (you can actually put the configuration in but will be read before
.Pa /etc/krb5.conf , .Pa /etc/krb5.conf ,
and then start the KDC with so it may override settings found there. Options specific to the KDC
.Fl -config-file= Ns Ar /etc/krb5.conf ) . only are found in the
All options should be in a section called .Dq [kdc]
.Dq kdc . section.
All the command-line options can preferably be added in the All the command-line options can preferably be added in the
configuration file. The only difference is the pre-authentication flag, configuration file. The only difference is the pre-authentication flag,
that has to be specified as: that has to be specified as:
@@ -139,5 +139,22 @@ An example of a config file:
v4-realm = FOO.SE v4-realm = FOO.SE
key-file = /key-file key-file = /key-file
.Ed .Ed
.Sh BUGS
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 operation require that you add and remove addresses, the best
option is probably 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:
.Bd -literal -offset indent
kdc --addresses=0.0.0.0 --ports="88/tcp"
.Ed
.Pp
There should be a way to specify protocol, port, and address triplets,
not just addresses and protocol, port tuples.
.Sh SEE ALSO .Sh SEE ALSO
.Xr kinit 1 .Xr kinit 1 ,
.Xr krb5.conf 5