2 VERIFY_KRB5_CONF(8) UNIX System Manager's Manual VERIFY_KRB5_CONF(8)
5 v
\bve
\ber
\bri
\bif
\bfy
\by_
\b_k
\bkr
\brb
\bb5
\b5_
\b_c
\bco
\bon
\bnf
\bf - checks krb5.conf for obvious errors
7 S
\bSY
\bYN
\bNO
\bOP
\bPS
\bSI
\bIS
\bS
8 v
\bve
\ber
\bri
\bif
\bfy
\by_
\b_k
\bkr
\brb
\bb5
\b5_
\b_c
\bco
\bon
\bnf
\bf _
\b[_
\bc_
\bo_
\bn_
\bf_
\bi_
\bg_
\b-_
\bf_
\bi_
\bl_
\be_
\b]
10 D
\bDE
\bES
\bSC
\bCR
\bRI
\bIP
\bPT
\bTI
\bIO
\bON
\bN
11 v
\bve
\ber
\bri
\bif
\bfy
\by_
\b_k
\bkr
\brb
\bb5
\b5_
\b_c
\bco
\bon
\bnf
\bf reads the configuration file _
\bk_
\br_
\bb_
\b5_
\b._
\bc_
\bo_
\bn_
\bf, or the file giv-
12 en on the command line, and parses it, thereby verifying that the syntax
13 is not correctly wrong.
15 If the file is syntactically correct, v
\bve
\ber
\bri
\bif
\bfy
\by_
\b_k
\bkr
\brb
\bb5
\b5_
\b_c
\bco
\bon
\bnf
\bf tries to verify
16 that the contents of the file is of relevant nature.
18 D
\bDI
\bIA
\bAG
\bGN
\bNO
\bOS
\bST
\bTI
\bIC
\bCS
\bS
19 Possible output from v
\bve
\ber
\bri
\bif
\bfy
\by_
\b_k
\bkr
\brb
\bb5
\b5_
\b_c
\bco
\bon
\bnf
\bf include:
21 <path>: failed to parse <something> as size/time/number/boolean
22 Usually means that <something> is misspelled, or that it contains
23 weird characters. The parsing done by v
\bve
\ber
\bri
\bif
\bfy
\by_
\b_k
\bkr
\brb
\bb5
\b5_
\b_c
\bco
\bon
\bnf
\bf is more
24 strict than the one performed by libkrb5, and so strings that
25 work in real life, might be reported as bad.
27 <path>: host not found (<hostname>)
28 Means that <path> is supposed to point to a host, but it can't be
31 <path>: unknown or wrong type
32 Means that <path> is either is a string when it should be a list,
33 vice versa, or just that v
\bve
\ber
\bri
\bif
\bfy
\by_
\b_k
\bkr
\brb
\bb5
\b5_
\b_c
\bco
\bon
\bnf
\bf is confused.
36 Means that <string> is not known by .
38 E
\bEN
\bNV
\bVI
\bIR
\bRO
\bON
\bNM
\bME
\bEN
\bNT
\bT
39 KRB5_CONFIG points to the configuration file to read.
42 /etc/krb5.conf Kerberos 5 configuration file
44 S
\bSE
\bEE
\bE A
\bAL
\bLS
\bSO
\bO
48 Since each application can put almost anything in the config file, it's
49 hard to come up with a water tight verification process. Most of the de-
50 fault settings are sanity checked, but this does not mean that every
51 problem is discovered, or that everything that is reported as a possible
52 problem actually is one. This tool should thus be used with some care.
54 It should warn about obsolete data, or bad practice, but currently
57 HEIMDAL August 30, 2001 1