MIT Kerberos defaults¶
General defaults¶
Description |
Default |
Environment |
---|---|---|
keytab file |
KRB5_KTNAME |
|
Client keytab file |
KRB5_CLIENT_KTNAME |
|
Kerberos config file krb5.conf |
|
KRB5_CONFIG |
KDC config file kdc.conf |
LOCALSTATEDIR |
KRB5_KDC_PROFILE |
GSS mechanism config file |
SYSCONFDIR |
GSS_MECH_CONFIG |
KDC database path (DB2) |
LOCALSTATEDIR |
|
Master key stash file |
LOCALSTATEDIR |
|
Admin server ACL file kadm5.acl |
LOCALSTATEDIR |
|
OTP socket directory |
RUNSTATEDIR |
|
Plugin base directory |
LIBDIR |
|
replay cache directory |
|
KRB5RCACHEDIR |
Master key default enctype |
|
|
Default keysalt list |
|
|
Permitted enctypes |
|
|
KDC default port |
88 |
|
Admin server port |
749 |
|
Password change port |
464 |
Replica KDC propagation defaults¶
This table shows defaults used by the kprop and kpropd programs.
Description |
Default |
Environment |
---|---|---|
kprop database dump file |
LOCALSTATEDIR |
|
kpropd temporary dump file |
LOCALSTATEDIR |
|
kdb5_util location |
SBINDIR |
|
kprop location |
SBINDIR |
|
kpropd ACL file |
LOCALSTATEDIR |
|
kprop port |
754 |
KPROP_PORT |
Default paths for Unix-like systems¶
On Unix-like systems, some paths used by MIT krb5 depend on parameters
chosen at build time. For a custom build, these paths default to
subdirectories of /usr/local
. When MIT krb5 is integrated into an
operating system, the paths are generally chosen to match the
operating system’s filesystem layout.
Description |
Symbolic name |
Custom build path |
Typical OS path |
---|---|---|---|
User programs |
BINDIR |
|
|
Libraries and plugins |
LIBDIR |
|
|
Parent of KDC state dir |
LOCALSTATEDIR |
|
|
Parent of KDC runtime dir |
RUNSTATEDIR |
|
|
Administrative programs |
SBINDIR |
|
|
Alternate krb5.conf dir |
SYSCONFDIR |
|
|
Default ccache name |
DEFCCNAME |
|
|
Default keytab name |
DEFKTNAME |
|
|
Default PKCS11 module |
PKCS11_MODNAME |
|
|
The default client keytab name (DEFCKTNAME) typically defaults to
FILE:/usr/local/var/krb5/user/%{euid}/client.keytab
for a custom
build. A native build will typically use a path which will vary
according to the operating system’s layout of /var
.