1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
1540
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582
1583
1584
1585
1586
1587
1588
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
1603
1604
1605
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695
1696
1697
1698
1699
1700
1701
1702
1703
1704
1705
1706
1707
1708
1709
1710
1711
1712
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
1732
1733
1734
1735
1736
1737
1738
1739
1740
1741
1742
1743
1744
1745
1746
1747
1748
1749
1750
1751
1752
1753
1754
1755
1756
1757
1758
1759
1760
1761
1762
1763
1764
1765
1766
1767
1768
1769
1770
1771
1772
1773
1774
1775
1776
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788
1789
1790
1791
1792
1793
1794
1795
1796
1797
1798
1799
1800
1801
1802
1803
1804
1805
1806
1807
1808
1809
1810
1811
1812
1813
1814
1815
1816
1817
1818
1819
1820
1821
1822
1823
1824
1825
1826
1827
1828
1829
1830
1831
1832
1833
1834
1835
1836
1837
1838
1839
1840
1841
1842
1843
1844
1845
1846
1847
1848
1849
1850
1851
1852
1853
1854
1855
1856
1857
1858
1859
1860
1861
1862
1863
1864
1865
1866
1867
1868
1869
1870
1871
1872
1873
1874
1875
1876
1877
1878
1879
1880
1881
1882
1883
1884
1885
1886
1887
1888
1889
1890
1891
1892
1893
1894
1895
1896
1897
1898
1899
1900
1901
1902
1903
1904
1905
1906
1907
1908
1909
1910
1911
1912
1913
1914
1915
1916
1917
1918
1919
1920
1921
1922
1923
1924
1925
1926
1927
1928
1929
1930
1931
1932
1933
1934
1935
1936
1937
1938
1939
1940
1941
1942
1943
1944
1945
1946
1947
1948
1949
1950
1951
1952
1953
1954
1955
1956
1957
1958
1959
1960
1961
1962
1963
1964
1965
1966
1967
1968
1969
1970
1971
1972
1973
1974
1975
1976
1977
1978
1979
1980
1981
1982
1983
1984
1985
1986
1987
1988
1989
1990
1991
1992
1993
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
2027
2028
2029
2030
2031
2032
2033
2034
2035
2036
2037
2038
2039
2040
2041
2042
2043
2044
2045
2046
2047
2048
2049
2050
2051
2052
2053
2054
2055
2056
2057
2058
2059
2060
2061
2062
2063
2064
2065
2066
2067
2068
2069
2070
2071
2072
2073
2074
2075
2076
2077
2078
2079
2080
2081
2082
2083
2084
2085
2086
2087
2088
2089
2090
2091
2092
2093
2094
2095
2096
2097
2098
2099
2100
2101
2102
2103
2104
2105
2106
2107
2108
2109
2110
2111
2112
2113
2114
2115
2116
2117
2118
2119
2120
2121
2122
2123
2124
2125
2126
2127
2128
2129
2130
2131
2132
2133
2134
2135
2136
2137
2138
2139
2140
2141
2142
2143
2144
2145
2146
2147
2148
2149
2150
2151
2152
2153
2154
2155
2156
2157
2158
2159
2160
2161
2162
2163
2164
2165
2166
2167
2168
2169
2170
2171
2172
2173
2174
2175
2176
2177
2178
2179
2180
2181
2182
2183
2184
2185
2186
2187
2188
2189
2190
2191
2192
2193
2194
2195
2196
2197
2198
2199
2200
2201
2202
2203
2204
2205
2206
2207
2208
2209
2210
2211
2212
2213
2214
2215
2216
2217
2218
2219
2220
2221
2222
2223
2224
2225
2226
2227
2228
2229
2230
2231
2232
2233
2234
2235
2236
2237
2238
2239
2240
2241
2242
2243
2244
2245
2246
2247
2248
2249
2250
2251
2252
2253
2254
2255
2256
2257
2258
2259
2260
2261
2262
2263
2264
2265
2266
2267
2268
2269
2270
2271
2272
2273
2274
2275
2276
2277
2278
2279
2280
2281
2282
2283
2284
2285
2286
2287
2288
2289
2290
2291
2292
2293
2294
2295
2296
2297
2298
2299
2300
2301
2302
2303
2304
2305
2306
2307
2308
2309
2310
2311
2312
2313
2314
2315
2316
2317
2318
2319
2320
2321
2322
2323
2324
2325
2326
2327
2328
2329
2330
2331
2332
2333
2334
2335
2336
2337
2338
2339
2340
2341
2342
2343
2344
2345
2346
2347
2348
2349
2350
2351
2352
2353
2354
2355
2356
2357
2358
2359
2360
2361
2362
2363
2364
2365
2366
2367
2368
2369
2370
2371
2372
2373
2374
2375
2376
2377
2378
2379
2380
2381
2382
2383
2384
2385
2386
2387
2388
2389
2390
2391
2392
2393
2394
2395
2396
2397
2398
2399
2400
2401
2402
2403
2404
2405
2406
2407
2408
2409
2410
2411
2412
2413
2414
2415
2416
2417
2418
2419
2420
2421
2422
2423
2424
2425
2426
2427
2428
2429
2430
2431
2432
2433
2434
2435
2436
2437
2438
2439
2440
2441
2442
2443
2444
2445
2446
2447
2448
2449
2450
2451
2452
2453
2454
2455
2456
2457
2458
2459
2460
2461
2462
2463
2464
2465
2466
2467
2468
2469
2470
2471
2472
2473
2474
2475
2476
2477
2478
2479
2480
2481
2482
2483
2484
2485
2486
2487
2488
2489
2490
2491
2492
2493
2494
2495
2496
2497
2498
2499
2500
2501
2502
2503
2504
2505
2506
2507
2508
2509
2510
2511
2512
2513
2514
2515
2516
2517
2518
2519
2520
2521
2522
2523
2524
2525
2526
2527
2528
2529
2530
2531
2532
2533
2534
2535
2536
2537
2538
2539
2540
2541
2542
2543
2544
2545
2546
2547
2548
2549
2550
2551
2552
2553
2554
2555
2556
2557
2558
2559
2560
2561
2562
2563
2564
2565
2566
2567
2568
2569
2570
2571
2572
2573
2574
2575
2576
2577
2578
2579
2580
2581
2582
2583
2584
2585
2586
2587
2588
2589
2590
2591
2592
2593
2594
2595
2596
2597
2598
2599
2600
2601
2602
2603
2604
2605
2606
2607
2608
2609
2610
2611
2612
2613
2614
2615
2616
2617
2618
2619
2620
2621
2622
2623
2624
2625
2626
2627
2628
2629
2630
2631
2632
2633
2634
2635
2636
2637
2638
2639
2640
2641
2642
2643
2644
2645
2646
2647
2648
2649
2650
2651
2652
2653
2654
2655
2656
2657
2658
2659
2660
2661
2662
2663
2664
2665
2666
2667
2668
2669
2670
2671
2672
2673
2674
2675
2676
2677
2678
2679
2680
2681
2682
2683
2684
2685
2686
2687
2688
2689
2690
2691
2692
2693
2694
2695
2696
2697
2698
2699
2700
2701
2702
2703
2704
2705
2706
2707
2708
2709
2710
2711
2712
2713
2714
2715
2716
2717
2718
2719
2720
2721
2722
2723
2724
2725
2726
2727
2728
2729
2730
2731
2732
2733
2734
2735
2736
2737
2738
2739
2740
2741
2742
2743
2744
2745
2746
2747
2748
2749
2750
2751
2752
2753
2754
2755
2756
2757
2758
2759
2760
2761
2762
2763
2764
2765
2766
2767
2768
2769
2770
2771
2772
2773
2774
2775
2776
2777
2778
2779
2780
2781
2782
2783
2784
2785
2786
2787
2788
2789
2790
2791
2792
2793
2794
2795
2796
2797
2798
2799
2800
2801
2802
2803
2804
2805
2806
2807
2808
2809
2810
2811
2812
2813
2814
2815
2816
2817
2818
2819
2820
2821
2822
2823
2824
2825
2826
2827
2828
2829
2830
2831
2832
2833
2834
2835
2836
2837
2838
2839
2840
2841
2842
2843
2844
2845
2846
2847
2848
2849
2850
2851
2852
2853
2854
2855
2856
2857
2858
2859
2860
2861
2862
2863
2864
2865
2866
2867
2868
2869
2870
2871
2872
2873
2874
2875
2876
2877
2878
2879
2880
2881
2882
2883
2884
2885
2886
2887
2888
2889
2890
2891
2892
2893
2894
2895
2896
2897
2898
2899
2900
2901
2902
2903
2904
2905
2906
2907
2908
2909
2910
2911
2912
2913
2914
2915
2916
2917
2918
2919
2920
2921
2922
2923
2924
2925
2926
2927
2928
2929
2930
2931
2932
2933
2934
2935
2936
2937
2938
2939
2940
2941
2942
2943
2944
2945
2946
2947
2948
2949
2950
2951
2952
2953
2954
2955
2956
2957
2958
2959
2960
2961
2962
2963
2964
2965
2966
2967
2968
2969
2970
2971
2972
2973
2974
2975
2976
2977
2978
2979
2980
2981
2982
2983
2984
2985
2986
2987
2988
2989
2990
2991
2992
2993
2994
2995
2996
2997
2998
2999
3000
3001
3002
3003
3004
3005
3006
3007
3008
3009
3010
3011
3012
3013
3014
3015
3016
3017
3018
3019
3020
3021
3022
3023
3024
3025
3026
3027
3028
3029
3030
3031
3032
3033
3034
3035
3036
3037
3038
3039
3040
3041
3042
3043
3044
3045
3046
3047
3048
3049
3050
3051
3052
3053
3054
3055
3056
3057
3058
3059
3060
3061
3062
3063
3064
3065
3066
3067
3068
3069
3070
3071
3072
3073
3074
3075
3076
3077
3078
3079
3080
3081
3082
3083
3084
3085
3086
3087
3088
3089
3090
3091
3092
3093
3094
3095
3096
3097
3098
3099
3100
3101
3102
3103
3104
3105
3106
3107
3108
3109
3110
3111
3112
3113
3114
3115
3116
3117
3118
3119
3120
3121
3122
3123
3124
3125
3126
3127
3128
3129
3130
3131
3132
3133
3134
3135
3136
3137
3138
3139
3140
3141
3142
3143
3144
3145
3146
3147
3148
3149
3150
3151
3152
3153
3154
3155
3156
3157
3158
3159
3160
3161
3162
3163
3164
3165
3166
3167
3168
3169
3170
3171
3172
3173
3174
3175
3176
3177
3178
3179
3180
3181
3182
3183
3184
3185
3186
3187
3188
3189
3190
3191
3192
3193
3194
3195
3196
3197
3198
3199
3200
3201
3202
3203
3204
3205
3206
3207
3208
3209
3210
3211
3212
3213
3214
3215
3216
3217
3218
3219
3220
3221
3222
3223
3224
3225
3226
3227
3228
3229
3230
3231
3232
3233
3234
3235
3236
3237
3238
3239
3240
3241
3242
3243
3244
3245
3246
3247
3248
3249
3250
3251
3252
3253
3254
3255
3256
3257
3258
3259
3260
3261
3262
3263
3264
3265
3266
3267
|
\input texinfo-suppl.tex % contains @doubleleftarrow{} definition
% this line must come *before* \input texinfo
\input texinfo @c -*-texinfo-*-
@c %**start of header
@c guide
@setfilename krb5-admin.info
@settitle Kerberos V5 System Administrator's Guide
@setchapternewpage odd @c chapter begins on next odd page
@c @setchapternewpage on @c chapter begins on next page
@c @smallbook @c Format for 7" X 9.25" paper
@c %**end of header
@paragraphindent 0
@iftex
@parskip 6pt plus 6pt
@end iftex
@include definitions.texinfo
@set EDITION 1.0
@set UPDATED June 16, 2000
@finalout @c don't print black warning boxes
@titlepage
@title @value{PRODUCT} System Administrator's Guide
@subtitle Release: @value{RELEASE}
@subtitle Document Edition: @value{EDITION}
@subtitle Last updated: @value{UPDATED}
@author @value{COMPANY}
@page
@vskip 0pt plus 1filll
@include copyright.texinfo
@end titlepage
@comment node-name, next, previous, up
@node Top, Copyright, (dir), (dir)
@ifinfo
This document describes how to administrate a @value{PRODUCT}
installation.
@c The master menu is updated using emacs19's M-x texinfo-all-menus-update
@c function. Don't forget to run M-x texinfo-every-node-update after
@c you add a new section or subsection, or after you've rearranged the
@c order of sections or subsections. Also, don't forget to add an @node
@c comand before each @section or @subsection! All you need to enter
@c is:
@c
@c @node New Section Name
@c @section New Section Name
@c
@c M-x texinfo-every-node-update will take care of calculating the
@c node's forward and back pointers.
@c
@c ---------------------------------------------------------------------
@menu
* Copyright::
* Introduction::
* How Kerberos Works::
* Configuration Files::
* Administrating Kerberos Database Entries::
* Application Servers::
* Backups of Secure Hosts::
* Bug Reporting::
* Appendix::
@end menu
@node Copyright, Introduction, Top, Top
@unnumbered Copyright
@include copyright.texinfo
@end ifinfo
@node Introduction, How Kerberos Works, Copyright, Top
@chapter Introduction
@menu
* Why Should I use Kerberos?::
* Documentation for Kerberos V5::
* Overview of This Guide::
@end menu
@node Why Should I use Kerberos?, Documentation for Kerberos V5, Introduction, Introduction
@section Why Should I use Kerberos?
Since Kerberos negotiates authenticated, and optionally encrypted,
communications between two points anywhere on the internet, it provides
a layer of security that is not dependent on which side of a firewall
either client is on. Since studies have shown that half of the computer
security breaches in industry happen from @i{inside} firewalls,
@value{PRODUCT} from @value{COMPANY} will play a vital role in the
security of your network.
@node Documentation for Kerberos V5, Overview of This Guide, Why Should I use Kerberos?, Introduction
@section Documentation for @value{PRODUCT}
@include document-list.texinfo
@node Overview of This Guide, , Documentation for Kerberos V5, Introduction
@section Overview of This Guide
The next chapter describes how Kerberos works.
Chapter three describes administration of the principals in the Kerberos
database.
Chapter four describes administrative programs for manipulating the
Kerberos database as a whole.
Chapter five describes issues to consider when adding an application
server to the database.
Chapter six describes our problem reporting system.
The appendices include sample configuration files, the list of Kerberos
error messages, and a complete list of the time zones understood by
@code{kadmin}.
@node How Kerberos Works, Configuration Files, Introduction, Top
@chapter How Kerberos Works
This section provides a simplified description of a general user's
interaction with the Kerberos system. This interaction happens
transparently---users don't need to know and probably don't care about
what's going on---but Kerberos administrators might find a schematic
description of the process useful. This description glosses over a lot
of details; for more information, see @i{Kerberos: An Authentication
Service for Open Network Systems}, a paper presented at Winter USENIX
1988, in Dallas, Texas. This paper can be retreived by FTP from
@code{athena-dist.mit.edu}, in the location:
@code{/pub/ATHENA/kerberos/doc/USENIX.ps}.
@menu
* Network Services and Their Client Programs::
* Kerberos Tickets::
* The Kerberos Database::
* Kerberos Realms::
* The Ticket-Granting Ticket::
* Network Services and the Master Database::
* The User/Kerberos Interaction::
* Definitions::
@end menu
@node Network Services and Their Client Programs, Kerberos Tickets, How Kerberos Works, How Kerberos Works
@section Network Services and Their Client Programs
In an environment that provides network services, you use @dfn{client}
programs to request @dfn{services} from @dfn{server} programs that are
somewhere on the network. Suppose you have logged in to a workstation
and you want to @samp{rlogin} to a typical UNIX host. You use the local
@samp{rlogin} client program to contact the remote machine's
@samp{rlogind} daemon.
@node Kerberos Tickets, The Kerberos Database, Network Services and Their Client Programs, How Kerberos Works
@section Kerberos Tickets
Under Kerberos, the @samp{klogind} daemon allows you to login to a
remote machine if you can provide @samp{klogind} a Kerberos ticket
which proves your identity. In addition to the ticket, you must also
have possession of the corresponding ticket session key. The
combination of a ticket and the ticket's session key is known as a credential.
Typically, a client program automatically obtains credentials
identifying the person using the client program. The credentials are
obtained from a Kerberos server that resides somewhere on the network.
A Kerberos server maintains a database of user, server, and password
information.
@node The Kerberos Database, Kerberos Realms, Kerberos Tickets, How Kerberos Works
@section The Kerberos Database
Kerberos will give you credentials only if you have an entry in the
Kerberos server's @dfn{Kerberos database}. Your database entry includes
your Kerberos @dfn{principal} (an identifying string, which is often
just your username), and your Kerberos password. Every Kerberos user
must have an entry in this database.
@node Kerberos Realms, The Ticket-Granting Ticket, The Kerberos Database, How Kerberos Works
@section Kerberos Realms
Each administrative domain will have its own Kerberos database, which
contains information about the users and services for that particular
site or administrative domain. This administrative domain is the
@dfn{Kerberos realm}.
Each Kerberos realm will have at least one Kerberos server, where the
master Kerberos database for that site or administrative domain is
stored. A Kerberos realm may also have one or more @dfn{slave servers},
which have read-only copies of the Kerberos database that are
periodically propagated from the master server. For more details on how
this is done, see the ``Set Up the Slave KDCs for Database Propagation''
and ``Propagate the Database to Each Slave KDC'' sections of the
@value{PRODUCT} Installation Guide.
@node The Ticket-Granting Ticket, Network Services and the Master Database, Kerberos Realms, How Kerberos Works
@section The Ticket-Granting Ticket
The @samp{kinit} command prompts for your password. If you enter it
successfully, you will obtain a @dfn{ticket-granting ticket} and a
@dfn{ticket session key} which gives you the right to use the ticket.
This combination of the ticket and its associated key is known as your
@dfn{credentials}. As illustrated below, client programs use your
ticket-granting ticket credentials in order to obtain client-specific
credentials as needed.
Your credentials are stored in a @dfn{credentials cache}, which is often
just a file in @code{/tmp}. The credentials cache is also called the
@dfn{ticket file}, especially in Kerberos V4 documentation. Note,
however, that a credentials cache does not have to be stored in a file.
@node Network Services and the Master Database, The User/Kerberos Interaction, The Ticket-Granting Ticket, How Kerberos Works
@section Network Services and the Master Database
The master database also contains entries for all network services that
require Kerberos authentication. Suppose that your site has a machine,
@samp{laughter.@value{PRIMARYDOMAIN}}, that requires Kerberos
authentication from anyone who wants to @samp{rlogin} to it. The host's
Kerberos realm is @samp{@value{PRIMARYREALM}}.
This service must be registered in the Kerberos database, using the
proper service name, which in this case is the @dfn{principal}:
@smallexample
host/laughter.@value{PRIMARYDOMAIN}@@@value{PRIMARYREALM}
@end smallexample
@noindent
The @samp{/} character separates the Kerberos @dfn{primary} (in this
case, @samp{host}) from the @dfn{instance} (in this case,
@samp{laughter.@value{PRIMARYDOMAIN}}); the @samp{@@} character separates
the realm name (in this case, @samp{@value{PRIMARYREALM}}) from the rest
of the principal. The primary, @samp{host}, denotes the name or type of
the service that is being offered: generic host-level access to the
machine. The instance, @samp{laughter.@value{PRIMARYDOMAIN}}, names the
specific machine that is offering this service. There will generally be
many different machines, each offering one particular type of service,
and the instance serves to give each one of these servers a different
Kerberos principal.
@menu
* The Keytab File::
@end menu
@node The Keytab File, , Network Services and the Master Database, Network Services and the Master Database
@subsection The Keytab File
For each service, there must also be a @dfn{service key} known only by
Kerberos and the service. On the Kerberos server, the service key is
stored in the Kerberos database.
On the server host, these service keys are stored in @dfn{key tables},
which are files known as @dfn{keytabs}.@footnote{Keytabs were called
@dfn{srvtabs} in Kerberos V4.} For example, the service keys used by
services that run as root are usually stored in the keytab file
@code{/etc/krb5.keytab}. @b{N.B.:} This service key is the equivalent
of the service's password, and must be kept secure. Data which is meant
to be read only by the service is encrypted using this key.
@node The User/Kerberos Interaction, Definitions, Network Services and the Master Database, How Kerberos Works
@section The User/Kerberos Interaction
Suppose that you walk up to a host intending to login to it, and then
@samp{rlogin} to the machine @samp{laughter}. Here's what happens:
@enumerate
@item
You login to the workstation and use the @samp{kinit} command to get a
ticket-granting ticket. This command prompts you for your Kerberos
password. (On systems running the @value{PRODUCT} @samp{login} program,
this may be done as part of the login process, not requiring the user to
run a separate program.)
@enumerate A
@item
The @samp{kinit} command sends your request to the Kerberos master
server machine. The server software looks for your principal name's
entry in the Kerberos database.
@item
If this entry exists, the Kerberos server creates and returns a
ticket-granting ticket and the key which allows you to use it, encrypted
by your password. If @samp{kinit} can decrypt the Kerberos reply using
the password you provide, it stores this ticket in a credentials cache
on your local machine for later use. The name of the credentials cache
can be specified in the @samp{KRB5CCNAME} environment variable. If this
variable is not set, the name of the file will be
@file{/tmp/krb5cc_<uid>}, where <uid> is your UNIX user-id, represented
in decimal format.
@end enumerate
@need 1500
@item
Now you use the @samp{rlogin} client to access the machine
@samp{laughter}.
@example
host% @b{rlogin laughter}
@end example
@enumerate A
@item
The @samp{rlogin} client checks your ticket file to see if you have a
ticket for the @samp{host} service for @samp{laughter}. You don't, so
@samp{rlogin} uses the credential cache's ticket-granting ticket to make
a request to the master server's ticket-granting service.
@item
This ticket-granting service receives the request for a ticket for
@samp{host/laughter.@value{PRIMARYDOMAIN}}, and looks in the master
database for an entry for @samp{host/laughter.@value{PRIMARYDOMAIN}}.
If the entry exists, the ticket-granting service issues you a ticket for
that service. That ticket is also cached in your credentials cache.
@item
The @samp{rlogin} client now sends that ticket to the @samp{laughter}
@samp{klogind} service program. The service program checks the ticket
by using its own service key. If the ticket is valid, it now knows your
identity. If you are allowed to login to @samp{laughter} (because your
username matches one in /etc/passwd, or your Kerberos principal is in
the appropriate @file{.k5login} file), @code{klogind} will let you
login.
@end enumerate
@end enumerate
@node Definitions, , The User/Kerberos Interaction, How Kerberos Works
@section Definitions
Following are definitions of some of the Kerberos terminology.
@include glossary.texinfo
@node Configuration Files, Administrating Kerberos Database Entries, How Kerberos Works, Top
@chapter Configuration Files
@menu
* krb5.conf::
* kdc.conf::
@end menu
@node krb5.conf, kdc.conf, Configuration Files, Configuration Files
@section krb5.conf
The @code{krb5.conf} file contains Kerberos configuration information,
including the locations of KDCs and admin servers for the Kerberos
realms of interest, defaults for the current realm and for Kerberos
applications, and mappings of hostnames onto Kerberos realms. Normally,
you should install your @code{krb5.conf} file in the directory
@code{/etc}. You can override the default location by setting the
environment variable @samp{KRB5_CONFIG}.
The @code{krb5.conf} file is set up in the style of a Windows INI file.
Sections are headed by the section name, in square brackets. Each
section may contain zero or more relations, of the form:
@smallexample
foo = bar
@end smallexample
@noindent
or
@smallexample
@group
fubar = @{
foo = bar
baz = quux
@}
@end group
@end smallexample
The @code{krb5.conf} file may contain any or all of the following seven
sections:
@table @b
@itemx libdefaults
Contains default values used by the Kerberos V5 library.
@itemx appdefaults
Contains default values used by Kerberos V5 applications.
@itemx realms
Contains subsections keyed by Kerberos realm names. Each subsection
describes realm-specific information, including where to find the
Kerberos servers for that realm.
@itemx domain_realm
Contains relations which map domain names and subdomains onto Kerberos
realm names. This is used by programs to determine what realm a host
should be in, given its fully qualified domain name.
@itemx logging
Contains relations which determine how Kerberos programs are to perform
logging.
@itemx capaths
Contains the authentication paths used with direct (nonhierarchical)
cross-realm authentication. Entries in this section are used by the
client to determine the intermediate realms which may be used in
cross-realm authentication. It is also used by the end-service when
checking the transited field for trusted intermediate realms.
@itemx kdc
For a KDC, may contain the location of the kdc.conf file.
@end table
@menu
* libdefaults::
* appdefaults::
* realms (krb5.conf)::
* domain_realm::
* logging::
* capaths::
* Sample krb5.conf File::
@end menu
@node libdefaults, appdefaults, krb5.conf, krb5.conf
@subsection [libdefaults]
The @code{libdefaults} section may contain any of the following
relations:
@table @b
@itemx default_realm
Identifies the default Kerberos realm for the client. Set its value to
your Kerberos realm.
@itemx default_tgs_enctypes
Identifies the supported list of session key encryption types that
should be returned by the KDC. The list may be delimited with commas or
whitespace. Currently, the supported encryption types are
"des3-hmac-sha1" and
"des-cbc-crc". Support for other encryption types is planned in the
future.
@itemx default_tkt_enctypes
Identifies the supported list of session key encryption
types that should be requested by the client. The format is the same as
for @emph{default_tkt_enctypes}. Again, the only supported encryption
types are "des3-hmac-sha1" and "des-cbc-crc".
@itemx clockskew
Sets the maximum allowable amount of clockskew in seconds that the
library will tolerate before assuming that a Kerberos message is
invalid. The default value is 300 seconds, or five minutes.
@itemx checksum_type
Used for compatability with DCE security servers which do not support
the default CKSUMTYPE_RSA_MD5 used by this version of Kerberos. A value
of 1 indicates the default checksum type. Use a value of 2 to use the
CKSUMTYPE_RSA_MD4 instead. This applies to DCE 1.1 and earlier.
@itemx ccache_type
Use this parameter on systems which are DCE clients, to specify the type
of cache to be created by kinit, or when forwarded tickets are received.
DCE and Kerberos can share the cache, but some versions of DCE do not
support the default cache as created by this version of Kerberos. Use a
value of 1 on DCE 1.0.3a systems, and a value of 2 on DCE 1.1 systems.
@itemx dns_lookup_kdc
Indicate whether DNS SRV records should be used to locate the KDCs and
other servers for a realm, if they are not listed in the information for
the realm. (Note that the @samp{admin_server} entry must be in the
file, because the DNS implementation for it is incomplete.)
Enabling this option does open up a type of denial-of-service attack, if
someone spoofs the DNS records and redirects you to another server.
However, it's no worse than a denial of service, because that fake KDC
will be unable to decode anything you send it (besides the initial
ticket request, which has no encrypted data), and anything the fake KDC
sends will not be trusted without verification using some secret that it
won't know.
If this option is not specified but @samp{dns_fallback} is, that value
will be used instead. If neither option is specified, the behavior
depends on configure-time options; if none were given, the default is to
enable this option. If the DNS support is not compiled in, this entry
has no effect.
@itemx dns_lookup_realm
Indicate whether DNS TXT records should be used to determine the
Kerberos realm of a host.
Enabling this option may permit a redirection attack, where spoofed DNS
replies persuade a client to authenticate to the wrong realm, when
talking to the wrong host (either by spoofing yet more DNS records or by
intercepting the net traffic). Depending on how the client software
manages hostnames, however, it could already be vulnerable to such
attacks. We are looking at possible ways to minimize or eliminate this
exposure. For now, we encourage more adventurous sites to try using
Secure DNS.
If this option is not specified but @samp{dns_fallback} is, that value
will be used instead. If neither option is specified, the behavior
depends on configure-time options; if none were given, the default is to
disable this option. If the DNS support is not compiled in, this entry
has no effect.
@itemx dns_fallback
General flag controlling the use of DNS for Kerberos information. If
both of the preceding options are specified, this option has no effect.
@end table
@node appdefaults, realms (krb5.conf), libdefaults, krb5.conf
@subsection [appdefaults]
Each tag in the [appdefaults] section names a Kerberos V5 application.
The value of the tag is a subsection with relations that define the
default behaviors for that application.
For example:
@smallexample
@group
[appdefaults]
kinit = @{
forwardable = true
@}
telnet = @{
forward = true
encrypt = true
autologin = true
@}
@end group
@end smallexample
The list of specifiable options for each application may be found in
that application's man pages. The application defaults specified here
are overridden by those specified in the [realms] section.
@node realms (krb5.conf), domain_realm, appdefaults, krb5.conf
@subsection [realms]
Each tag in the [realms] section of the file is the name of a Kerberos
realm. The value of the tag is a subsection with relations that define
the properties of that particular realm. For each realm, the following
tags may be specified in the realm's subsection:
@table @b
@itemx kdc
The name of a host running a KDC for that realm. An optional port
number (separated from the hostname by a colon) may be included.
@itemx admin_server
Identifies the host where the administration server is running.
Typically, this is the master Kerberos server.
@itemx application defaults
Application defaults that are specific to a particular realm may be
specified within that realm's tag. Realm-specific application defaults
override the global defaults specified in the [appdefaults] section.
@end table
@node domain_realm, logging, realms (krb5.conf), krb5.conf
@subsection [domain_realm]
The [domain_realm] section provides a translation from a domain name or
hostname to a Kerberos realm name. The tag name can be a host name, or
a domain name, where domain names are indicated by a prefix of a period
(@samp{.}). The value of the relation is the Kerberos realm name for
that particular host or domain. Host names and domain names should be
in lower case.
If no translation entry applies, the host's realm is considered to be
the hostname's domain portion converted to upper case. For example, the
following [domain_realm] section:
@smallexample
@group
[domain_realm]
@ifset MIT
.mit.edu = ATHENA.MIT.EDU
@end ifset
@value{PRIMARYDOMAIN} = @value{PRIMARYREALM}
crash.@value{PRIMARYDOMAIN} = TEST.@value{PRIMARYREALM}
@value{SECONDDOMAIN} = @value{SECONDREALM}
@end group
@end smallexample
@noindent
maps crash.@value{PRIMARYDOMAIN} into the TEST.@value{PRIMARYREALM}
realm. All other hosts in the @value{PRIMARYDOMAIN} domain will map by
default to the @value{PRIMARYREALM} realm, and all hosts in the
@value{SECONDDOMAIN} domain will map by default into the
@value{SECONDREALM} realm. Note the entries for the hosts
@value{PRIMARYDOMAIN} and @value{SECONDDOMAIN}. Without these entries,
@ifset CYGNUS
these hosts would be mapped into the Kerberos realms @samp{COM} and
@end ifset
@ifclear CYGNUS
these hosts would be mapped into the Kerberos realms @samp{EDU} and
@end ifclear
@samp{ORG}, respectively.
@node logging, capaths, domain_realm, krb5.conf
@subsection [logging]
The [logging] section indicates how a particular entity is to perform
its logging. The relations in this section assign one or more values to
the entity name. Currently, the following entities are used:
@table @b
@itemx admin_server
These entries specify how the administrative server
is to perform its logging.
@itemx default
These entries specify how to perform logging in the
absence of explicit specifications otherwise.
@end table
Values are of the following forms:
@table @b
@itemx FILE=<filename>
@itemx FILE:<filename>
This value causes the entity's logging messages to go to the specified
file. If the @samp{=} form is used, the file is overwritten. If the
@samp{:} form is used, the file is appended to.
@itemx STDERR
This value causes the entity's logging messages to go to its standard
error stream.
@itemx CONSOLE
This value causes the entity's logging messages to go to the console, if
the system supports it.
@itemx DEVICE=<devicename>
This causes the entity's logging messages to go to the specified device.
@itemx SYSLOG[:<severity>[:<facility>]]
This causes the entity's logging messages to go to the system log.
The @dfn{severity} argument specifies the default severity of system log
messages. This may be any of the following severities supported by the
@code{syslog(3)} call, minus the LOG_ prefix: LOG_EMERG, LOG_ALERT,
LOG_CRIT, LOG_ERR, LOG_WARNING, LOG_NOTICE, LOG_INFO, and LOG_DEBUG.
For example, a value of @samp{CRIT} would specify LOG_CRIT severity.
The facility argument specifies the facility under which the messages
are logged. This may be any of the following facilities supported by
the syslog(3) call minus the LOG_ prefix: LOG_KERN, LOG_USER, LOG_MAIL,
LOG_DAEMON, LOG_AUTH, LOG_LPR, LOG_NEWS, LOG_UUCP, LOG_CRON, and
LOG_LOCAL0 through LOG_LOCAL7.
If no severity is specified, the default is ERR. If no facility is
specified, the default is AUTH.
@end table
In the following example, the logging messages from the KDC will go to
the console and to the system log under the facility LOG_DAEMON with
default severity of LOG_INFO; and the logging messages from the
administrative server will be appended to the file /var/adm/kadmin.log
and sent to the device /dev/tty04.
@smallexample
@group
[logging]
kdc = CONSOLE
kdc = SYSLOG:INFO:DAEMON
admin_server = FILE:/var/adm/kadmin.log
admin_server = DEVICE=/dev/tty04
@end group
@end smallexample
@node capaths, Sample krb5.conf File, logging, krb5.conf
@subsection [capaths]
In order to perform direct (non-hierarchical) cross-realm
authentication, a database is needed to construct the authentication
paths between the realms. This section defines that database.
A client will use this section to find the authentication path between
its realm and the realm of the server. The server will use this section
to verify the authentication path used be the client, by checking the
transited field of the received ticket.
There is a tag for each participating realm, and each tag has subtags
for each of the realms. The value of the subtags is an intermediate
realm which may participate in the cross-realm authentication. The
subtags may be repeated if there is more then one intermediate realm. A
value of "." means that the two realms share keys directly, and no
intermediate realms should be allowd to participate.
There are n**2 possible entries in this table, but only those entries
which will be needed on the client or the server need to be present.
The client needs a tag for its local realm, with subtags for all the
realms of servers it will need to authenticate with. A server needs a
tag for each realm of the clients it will serve.
For example, ANL.GOV, PNL.GOV, and NERSC.GOV all wish to use the ES.NET
realm as an intermediate realm. ANL has a sub realm of TEST.ANL.GOV
which will authenticate with NERSC.GOV but not PNL.GOV. The [capath]
section for ANL.GOV systems would look like this:
@smallexample
@group
[capaths]
ANL.GOV = @{
TEST.ANL.GOV = .
PNL.GOV = ES.NET
NERSC.GOV = ES.NET
ES.NET = .
@}
TEST.ANL.GOV = @{
ANL.GOV = .
@}
PNL.GOV = @{
ANL.GOV = ES.NET
@}
NERSC.GOV = @{
ANL.GOV = ES.NET
@}
ES.NET = @{
ANL.GOV = .
@}
@end group
@end smallexample
The [capath] section of the configuration file used on NERSC.GOV systems
would look like this:
@smallexample
@group
[capaths]
NERSC.GOV = @{
ANL.GOV = ES.NET
TEST.ANL.GOV = ES.NET
TEST.ANL.GOV = ANL.GOV
PNL.GOV = ES.NET
ES.NET = .
@}
ANL.GOV = @{
NERSC.GOV = ES.NET
@}
PNL.GOV = @{
NERSC.GOV = ES.NET
@}
ES.NET = @{
NERSC.GOV = .
@}
TEST.ANL.GOV = @{
NERSC.GOV = ANL.GOV
NERSC.GOV = ES.NET
@}
@end group
@end smallexample
In the above examples, the ordering is not important, except when the
same subtag name is used more then once. The client will use this to
determing the path. (It is not important to the server, since the
transited field is not sorted.)
This feature is not currently supported by DCE. DCE security servers
can be used with Kerberized clients and servers, but versions prior to
DCE 1.1 did not fill in the transited field, and should be used with
caution.
@node Sample krb5.conf File, , capaths, krb5.conf
@subsection Sample krb5.conf File
Here is an example of a generic @code{krb5.conf} file:
@smallexample
@group
[libdefaults]
ticket_lifetime = 600
default_realm = @value{PRIMARYREALM}
default_tkt_enctypes = des3-hmac-sha1 des-cbc-crc
default_tgs_enctypes = des3-hmac-sha1 des-cbc-crc
[realms]
@value{PRIMARYREALM} = @{
kdc = @value{KDCSERVER}.@value{PRIMARYDOMAIN}
kdc = @value{KDCSLAVE1}.@value{PRIMARYDOMAIN}
kdc = @value{KDCSLAVE2}.@value{PRIMARYDOMAIN}
admin_server = @value{KDCSERVER}.@value{PRIMARYDOMAIN}
default_domain = @value{PRIMARYDOMAIN}
@}
@value{SECONDREALM} = @{
kdc = @value{KDCSERVER}.@value{SECONDDOMAIN}
kdc = @value{KDCSLAVE1}.@value{SECONDDOMAIN}
admin_server = @value{KDCSERVER}.@value{SECONDDOMAIN}
@}
[domain_realm]
@ifset MIT
.mit.edu = ATHENA.MIT.EDU
@end ifset
@value{PRIMARYDOMAIN} = @value{PRIMARYREALM}
@end group
@end smallexample
@iftex
@vfill
@end iftex
@node kdc.conf, , krb5.conf, Configuration Files
@section kdc.conf
The @code{kdc.conf} file contains KDC configuration information,
including defaults used when issuing Kerberos tickets. Normally, you
should install your @code{kdc.conf} file in the directory
@code{@value{ROOTDIR}/var/krb5kdc}. You can override the default
location by setting the environment variable @samp{KRB5_KDC_PROFILE}.
The @code{kdc.conf} file is set up in the same format as the
@code{krb5.conf} file. (@xref{krb5.conf}.) The @code{kdc.conf} file
may contain any or all of the following three sections:
@table @b
@itemx kdcdefaults
Contains default values for overall behavior of the KDC.
@itemx realms
Contains subsections keyed by Kerberos realm names. Each subsection
describes realm-specific information, including where to find the
Kerberos servers for that realm.
@itemx logging
Contains relations which determine how Kerberos programs are to perform
logging.
@end table
@menu
* kdcdefaults::
* realms (kdc.conf)::
* Sample kdc.conf File::
@end menu
@node kdcdefaults, realms (kdc.conf), kdc.conf, kdc.conf
@subsection [kdcdefaults]
The following relation is defined in the [kdcdefaults] section:
@table @b
@itemx kdc_ports
This relation lists the ports on which the Kerberos server should listen
by default. This list is a comma separated list of integers. If this
relation is not specified, the compiled-in default is usually port 88
(the assigned Kerberos port) and port 750 (the port used by Kerberos
V4).
@end table
@node realms (kdc.conf), Sample kdc.conf File, kdcdefaults, kdc.conf
@subsection [realms]
Each tag in the [realms] section of the file names a Kerberos realm.
The value of the tag is a subsection where the relations in that
subsection define KDC parameters for that particular realm.
For each realm, the following tags may be specified in the [realms]
subsection:
@table @b
@itemx acl_file
(String.) Location of the access control list (acl) file that kadmin
uses to determine which principals are allowed which permissions on the
database. The default is @code{@value{ROOTDIR}/var/krb5kdc/kadm5.acl}.
@itemx admin_keytab
(String.) Location of the keytab file that kadmin uses to authenticate
to the database. The default is
@code{@value{ROOTDIR}/var/krb5kdc/kadm5.keytab}.
@itemx database_name
(String.) Location of the Kerberos database for this realm. The
default is @* @code{@value{ROOTDIR}/var/krb5kdc/principal}.
@itemx default_principal_expiration
(Absolute time string.) Specifies the default expiration date of
principals created in this realm.
@itemx default_principal_flags
(Flag string.) Specifies the default attributes of principals created
in this realm.
@itemx dict_file
(String.) Location of the dictionary file containing strings that are
not allowed as passwords. The default is
@code{@value{ROOTDIR}/var/krb5kdc/kadm5.dict}.
@itemx kadmind_port
(Port number.) Specifies the port that the kadmind daemon is to listen
for this realm. The assigned port for kadmind is 749.
@itemx key_stash_file
(String.) Specifies the location where the master key has been stored
(via @code{kdb5_util stash}). The default is
@code{@value{ROOTDIR}/var/krb5kdc/.k5.@i{REALM}}, where @i{REALM} is the
Kerberos realm.
@itemx kdc_ports
(String.) Specifies the list of ports that the KDC is to listen to for
this realm. By default, the value of kdc_ports as specified in the
[kdcdefaults] section is used.
@itemx master_key_name
(String.) Specifies the name of the master key.
@itemx master_key_type
(Key type string.) Specifies the master key's key type. Either
"des3-hmac-sha1" or
"des-cbc-crc" may be used at this time.
@itemx max_life
(Delta time string.) Specifes the maximum time period for which a
ticket may be valid in this realm.
@itemx max_renewable_life
(Delta time string.) Specifies the maximum time period during which a
valid ticket may be renewed in this realm.
@itemx supported_enctypes
List of key:salt strings. Specifies the default key/salt combinations
of principals for this realm. Any principals created through
@code{kadmin} will have keys of these types. If you do not yet wish to
enable triple-DES support, you should set this tag to
@samp{des-cbc-crc:normal des-cbc-crc:v4}; otherwise, put
@samp{des3-hmac-sha1:normal} at the beginning of the list.
@itemx kdc_supported_enctypes
List of key:salt strings. Specifies the permitted key/salt combinations
of principals for this realm. You should set this tag to
@samp{des3-hmac-sha1:normal des-cbc-crc:normal des-cbc-crc:v4}.
@itemx reject_bad_transit
A boolean value (@code{true}, @code{false}). If set to @code{true}, the
KDC will check the list of transited realms for cross-realm tickets
against the transit path computed from the realm names and the
@code{capaths} section of its @code{krb5.conf} file; if the path in the
ticket to be issued contains any realms not in the computed path, the
ticket will not be issued, and an error will be returned to the client
instead. If this value is set to @code{false}, such tickets will be
issued anyways, and it will be left up to the application server to
validate the realm transit path.
If the @code{disable-transited-check} flag is set in the incoming
request, this check is not performed at all. Having the
@code{reject_bad_transit} option will cause such ticket requests to be
rejected always.
This transit path checking and config file option currently apply only
to TGS requests.
Earlier versions of the MIT release (before 1.2.3) had bugs in the
application server support such that the server-side checks may not be
performed correctly. We recommend turning this option on, unless you
know that all application servers in this realm have been updated to
fixed versions of the software, and for whatever reason, you don't want
the KDC to do the validation.
This is a per-realm option so that multiple-realm KDCs may control it
separately for each realm, in case (for example) one realm has had the
software on its application servers updated but another has not.
This option defaults to @code{true}.
@end table
@node Sample kdc.conf File, , realms (kdc.conf), kdc.conf
@subsection Sample kdc.conf File
Here's an example of a @code{kdc.conf} file:
@smallexample
@group
[kdcdefaults]
kdc_ports = 88
[realms]
@value{PRIMARYREALM} = @{
kadmind_port = 749
max_life = 10h 0m 0s
max_renewable_life = 7d 0h 0m 0s
master_key_type = des3-hmac-sha1
supported_enctypes = des3-hmac-sha1:normal des-cbc-crc:normal des-cbc-crc:v4
kdc_supported_enctypes = des3-hmac-sha1:normal des-cbc-crc:normal des-cbc-crc:v4
@}
[logging]
kdc = FILE:@value{ROOTDIR}/var/krb5kdc/kdc.log
admin_server = FILE:@value{ROOTDIR}/var/krb5kdc/kadmin.log
@end group
@end smallexample
@node Administrating Kerberos Database Entries, Application Servers, Configuration Files, Top
@chapter Administrating the Kerberos Database
Your Kerberos database contains all of your realm's Kerberos principals,
their passwords, and other administrative information about each
principal. For the most part, you will use the @code{kdb5_util} program
to manipulate the Kerberos database as a whole, and the @code{kadmin}
program to make changes to the entries in the database. (One notable
exception is that users will use the @code{kpasswd} program to change
their own passwords.) The @code{kadmin} program has its own
command-line interface, to which you type the database administrating
commands.
@code{Kdb5_util} provides a means to create, delete, load, or dump a
Kerberos database. It also includes a command to stash a copy of the
master database key in a file on a KDC, so that the KDC can authenticate
itself to the @code{kadmind} and @code{krb5kdc} daemons at boot time.
@code{Kadmin} provides for the maintenance of Kerberos principals, KADM5
policies, and service key tables (keytabs). It exists as both a
Kerberos client, @code{kadmin}, using Kerberos authentication and an
RPC, to operate securely from anywhere on the network, and as a local
client, @code{kadmin.local}, intended to run directly on the KDC without
Kerberos authentication. Other than the fact that the remote client
uses Kerberos to authenticate the person using it, the functionalities
of the two versions are identical. The local version is necessary to
enable you to set up enough of the database to be able to use the remote
version. It replaces the now obsolete @code{kdb5_edit} (except for
database dump and load, which are provided by @code{kdb5_util}).
The remote version authenticates to the KADM5 server using the service
principal @code{kadmin/admin}. If the credentials cache contains a
ticket for the @code{kadmin/admin} principal, and the @samp{-c ccache}
option is specified, that ticket is used to authenticate to KADM5.
Otherwise, the @samp{-p} and @samp{-k} options are used to specify the
client Kerberos principal name used to authenticate. Once kadmin has
determined the principal name, it requests a @code{kadmin/admin}
Kerberos service ticket from the KDC, and uses that service ticket to
authenticate to KADM5.
@menu
* Kadmin Options::
* Date Format::
* Principals::
* Policies::
* Dumping a Kerberos Database to a File::
* Restoring a Kerberos Database from a Dump File::
* Creating a Stash File::
* Creating and Destroying a Kerberos Database::
@end menu
@node Kadmin Options, Date Format, Administrating Kerberos Database Entries, Administrating Kerberos Database Entries
@section Kadmin Options
You can invoke @code{kadmin} with any of the following options:
@table @b
@item @b{-r} @i{REALM}
Use @i{REALM} as the default Kerberos realm for the database.
@item @b{-p} @i{principal}
Use the Kerberos principal @i{principal} to authenticate to Kerberos.
If this option is not given, @code{kadmin} will append @code{admin} to
either the primary principal name, the environment variable USER, or to
the username obtained grom @code{getpwuid}, in order of preference.
@item @b{-k} @i{keytab}
Use the keytab @i{keytab} to decrypt the KDC response instead of
prompting for a password on the TTY. In this case, the principal will
be @samp{host/@i{hostname}}.
@item @b{-c} @i{credentials cache}
Use @i{credentials_cache} as the credentials cache. The credentials
cache should contain a service ticket for the @code{kadmin/admin}
service, which can be acquired with the @code{kinit} program. If this
option is not specified, @code{kadmin} requests a new service ticket
from the KDC, and stores it in its own temporary ccache.
@item @b{-w} @i{password}
Use @i{password} as the password instead of prompting for one on the
TTY. Note: placing the password for a Kerberos principal with
administration access into a shell script can be dangerous if
unauthorized users gain read access to the script.
@item @b{-q} @i{query}
Pass @i{query} directly to @code{kadmin}. This is useful for writing
scripts that pass specific queries to @code{kadmin}.
@item @b{-e} @i{"enctypes ..."}
@b{(For @code{kadmin.local} only.)}
Sets the list of cryptosystem and salt types to be used for any new keys
created. Available types include @samp{des3-cbc-sha1:normal},
@samp{des-cbc-crc:normal}, and @samp{des-cbc-crc:v4}.
@end table
@node Date Format, Principals, Kadmin Options, Administrating Kerberos Database Entries
@section Date Format
Many of the @code{kadmin} commands take a duration or time as an
argument. The date can appear in a wide variety of formats, such as:
@smallexample
@group
"15 minutes"
"7 days"
"1 month"
"2 hours"
"400000 seconds"
"next year"
"this Monday"
"next Monday"
yesterday
tomorrow
now
"second Monday"
fortnight
"3/31/1992 10:00:07 PST"
"January 23, 2007 10:05pm"
"22:00 GMT"
@end group
@end smallexample
Two-digit years are allowed in places, but the use of this form is not
recommended.
Note that if the date specification contains spaces, you must enclose it
in double quotes. Note also that you cannot use a number without a
unit. (I.e., ``"60 seconds"'' is correct, but ``60'' is incorrect.)
All keywords are case-insensitive. The following is a list of all of
the allowable keywords.
@table @b
@item Months
january, jan, february, feb, march, mar, april, apr, may, june, jun,
july, jul, august, aug, september, sept, sep, october, oct, november,
nov, december, dec
@item Days
sunday, sun, monday, mon, tuesday, tues, tue, wednesday, wednes, wed,
thursday, thurs, thur, thu, friday, fri, saturday, sat
@item Units
year, month, fortnight, week, day, hour, minute, min, second, sec
@item Relative
tomorrow, yesterday, today, now, last, this, next, first, third, fourth,
fifth, sixth, seventh, eighth, ninth, tenth, eleventh, twelfth, ago
@item Time Zones
@code{kadmin} recognizes abbreviations for most of the world's time
zones. A complete listing appears in @ref{kadmin Time Zones}.
@item 12-hour Time Delimiters
am, pm
@end table
@node Principals, Policies, Date Format, Administrating Kerberos Database Entries
@section Principals
Each entry in the Kerberos database contains a Kerberos principal
(@pxref{Definitions}) and the attributes and policies associated with
that principal.
@menu
* Retrieving Information About a Principal::
* Privileges::
* Adding or Modifying Principals::
* Deleting Principals::
* Changing Passwords::
@end menu
@node Retrieving Information About a Principal, Privileges, Principals, Principals
@subsection Retrieving Information About a Principal
@menu
* Attributes::
* Retrieving a List of Principals::
@end menu
@node Attributes, Retrieving a List of Principals, Retrieving Information About a Principal, Retrieving Information About a Principal
@subsubsection Attributes
To retrieve a listing of the attributes and/or policies associated with
a principal, use the @code{kadmin} @code{get_principal} command, which
requires the ``inquire'' administrative privilege. The syntax is:
@smallexample
@b{get_principal} @i{principal}
@end smallexample
@noindent The @code{get_principal} command has the alias @code{getprinc}.
For example, suppose you wanted to view the attributes of the principals
@* @code{@value{RANDOMUSER1}/root@@@value{PRIMARYREALM}} and
@code{systest@@@value{PRIMARYREALM}}. You would type:
@smallexample
@group
@b{shell%} kadmin
@b{kadmin:} getprinc @value{RANDOMUSER1}/root
@b{Principal: @value{RANDOMUSER1}/root@@@value{PRIMARYREALM}
Key version: 3
Maximum life: 1 day 00:00:00
Maximum renewable life: 7 days 00:00:00
Master key version: 1
Expires: Mon Jan 18 22:14:07 EDT 2038
Password expires: Mon Sep 19 14:40:00 EDT 1996
Password last changed: Mon Jan 31 02:06:40 EDT 1996
Last modified: by @value{ADMINUSER}/admin@@@value{PRIMARYREALM}
on Wed Jul 13 18:27:08 EDT 1996
Attributes: DISALLOW_FORWARDABLE, DISALLOW_PROXIABLE,
REQUIRES_HW_AUTH
Salt type: DEFAULT
kadmin:}
@end group
@end smallexample
The @code{get_principal} command has a @code{-terse} option, which lists
the fields as a quoted, tab-separated string. For example:
@smallexample
@group
@b{kadmin:} getprinc -terse systest
@b{systest@@@value{PRIMARYREALM} 3 86400 604800 1
785926535 753241234 785900000
@value{ADMINUSER}/admin@@@value{PRIMARYREALM} 786100034 0
0
kadmin:}
@end group
@end smallexample
@node Retrieving a List of Principals, , Attributes, Retrieving Information About a Principal
@subsubsection Retrieving a List of Principals
To generate a listing of principals, use the @code{kadmin}
@code{list_principals} command, which requires the ``list'' privilege.
The syntax is:
@smallexample
@b{list_principals} [@i{expression}]
@end smallexample
@noindent where @i{expression} is a shell-style glob expression that can
contain the characters @samp{*}, @samp{?}, @samp{[}, and @samp{]}. All
policy names matching the expression are displayed. The
@code{list_principals} command has the alias @code{listprincs}. For
example:
@smallexample
@group
@b{kadmin:} listprincs test*
@b{test3@@@value{PRIMARYDOMAIN}
test2@@@value{PRIMARYDOMAIN}
test1@@@value{PRIMARYDOMAIN}
testuser@@@value{PRIMARYDOMAIN}
kadmin:}
@end group
@end smallexample
@noindent If no expression is provided, all principals are printed.
@node Privileges, Adding or Modifying Principals, Retrieving Information About a Principal, Principals
@subsection Privileges
Administrative privileges for the Kerberos database are stored in the
file @code{kadm5.acl}. Each line of the file contains a principal, the
privileges that principal has, and optionally the target to which those
permissions apply. The privileges are represented by single letters;
UPPER-CASE letters represent negative permissions. The permissions are:
@table @b
@itemx a
allows the addition of principals or policies in the database.
@itemx A
disallows the addition of principals or policies in the database.
@itemx d
allows the deletion of principals or policies in the database.
@itemx D
disallows the deletion of principals or policies in the database.
@itemx m
allows the modification of principals or policies in the database.
@itemx M
disallows the modification of principals or policies in the database.
@itemx c
allows the changing of passwords for principals in the database.
@itemx C
disallows the changing of passwords for principals in the database.
@itemx i
allows inquiries to the database.
@itemx I
disallows inquiries to the database.
@itemx l
allows the listing of principals or policies in the database.
@itemx L
disallows the listing of principals or policies in the database.
@itemx *
All privileges (admcil).
@itemx x
All privileges (admcil); identical to ``*''.
@end table
Principals in this file can include the @b{*} wildcard. Here is an
example of a @code{kadm5.acl} file. Note that order is important;
permissions are determined by the first matching entry.
@smallexample
@group
*/admin@@@value{PRIMARYREALM} *
@value{ADMINUSER}@@@value{PRIMARYREALM} ADMCIL
@value{ADMINUSER}/*@@@value{PRIMARYREALM} il
@value{RANDOMUSER1}/root@@@value{PRIMARYREALM} cil */root@@@value{PRIMARYREALM}
*/*@@@value{PRIMARYREALM} i
@end group
@end smallexample
@noindent In the above file, any principal with an @code{admin} instance
has all administrative privileges. The user @code{@value{ADMINUSER}}
has all permissions with his @code{admin} instance,
@code{@value{ADMINUSER}/admin@@@value{PRIMARYREALM}} (matches the first
line). He has no permissions at all with his @code{null} instance,
@code{@value{ADMINUSER}@@@value{PRIMARYREALM}} (matches the second
line). He has @i{inquire} and @i{list} permissions with any other
instance (matches the third line). When @code{@value{RANDOMUSER1}} is
using her @code{root}
instance, @code{@value{RANDOMUSER1}/root@@@value{PRIMARYREALM}}, she has
@i{change password}, @i{inquire}, and @i{list} privileges for any other
principal that has the instance @code{root}. Finally, any principal in
the realm @code{@value{PRIMARYREALM}} (except for
@code{@value{ADMINUSER}@@@value{PRIMARYREALM}}, as mentioned above)
has @i{inquire} privileges.
@node Adding or Modifying Principals, Deleting Principals, Privileges, Principals
@subsection Adding or Modifying Principals
To add a principal to the database, use the kadmin @code{add_principal}
command, which requires the ``add'' administrative privilege. This
function creates the new principal and, if neither the -policy nor
-clearpolicy options are specified and the policy ``default'' exists,
assigns it that policy. The syntax is:
@smallexample
@b{kadmin:} add_principal [@i{options}] @i{principal}
@end smallexample
To modify attributes of a principal, use the kadmin
@code{modify_principal} command, which requires the ``modify''
administrative privilege. The syntax is:
@smallexample
@b{kadmin:} modify_principal [@i{options}] @i{principal}
@end smallexample
@noindent
@code{add_principal} has the aliases @code{addprinc} and
@code{ank}@footnote{@code{ank} was the short form of the equivalent
command using the deprecated @code{kadmin5} database administrative
tool. It has been kept. @code{modify_principal} has the alias @code{modprinc}.}
The @code{add_principal} and @code{modify_principal} commands take the
following switches:
@table @b
@item -salt @i{salttype}
Uses the specified salt for generating the key. The valid salt types
are:
@itemize @bullet
@item full_name (aliases ``v5_salt'' and ``normal''; this is the default)
@item name_only
@item realm_only
@item no_salt (alias ``v4_salt'')
@end itemize
@item -clearpolicy
For @code{modify_principal}, removes the current policy from a
principal. For @code{add_principal}, suppresses the automatic
assignment of the policy ``default''.
@item -expire @i{date}
Sets the expiration date of the principal to @i{date}.
@item -pwexpire @i{date}
Sets the expiration date of the password to @i{date}.
@item -maxlife @i{maxlife}
Sets the maximum ticket life of the principal to @i{maxlife}.
@item -kvno @i{number}
Explicity sets the key version number to @i{number}. @value{COMPANY}
does not recommend doing this unless there is a specific reason.
@item -policy @i{policy}
Sets the policy used by this principal. (@xref{Policies}.) With
@code{modify_principal}, the current policy assigned to the principal is
set or changed. With @code{add_principal}, if this option is not
supplied, the -clearpolicy is not specified, and the policy ``default''
exists, that policy is assigned. If a principal is created with no
policy, @code{kadmin} will print a warning message.
@item @{-|+@}allow_postdated
The ``-allow_postdated'' option prohibits this principal from obtaining
postdated tickets. ``+allow_postdated'' clears this flag. In effect,
``-allow_postdated'' sets the KRB5_KDB_DISALLOW_POSTDATED flag on the
principal in the database.
@item @{-|+@}allow_forwardable
The ``-allow_forwardable'' option prohibits this principal from
obtaining forwardable tickets. ``+allow_forwardable'' clears this flag.
In effect, ``-allow_forwardable'' sets the KRB5_KDB_DISALLOW_FORWARDABLE
flag on the principal in the database.
@item @{-|+@}allow_renewable
The ``-allow_renewable'' option prohibits this principal from obtaining
renewable tickets. ``+allow_renewable'' clears this flag. In effect,
``-allow_renewable'' sets the KRB5_KDB_DISALLOW_RENEWABLE flag on the
principal in the database.
@item @{-|+@}allow_proxiable
The ``-allow_proxiable'' option prohibits this principal from obtaining
proxiable tickets. ``+allow_proxiable'' clears this flag. In effect,
``-allow_proxiable'' sets the @* KRB5_KDB_DISALLOW_PROXIABLE flag. on
the principal in the database.
@item @{-|+@}allow_dup_skey
The ``-allow_dup_skey'' option disables user-to-user authentication for
this principal by prohibiting this principal from obtaining a session
key for another user. ``+allow_dup_skey'' clears this flag. In effect,
``-allow_dup_skey'' sets the @* KRB5_KDB_DISALLOW_DUP_SKEY flag on the
principal in the database.
@item @{-|+@}requires_preauth
The ``+requires_preauth'' option requires this principal to
preauthenticate before being allowed to kinit. -requires_preauth clears
this flag. In effect, +requires_preauth sets the
KRB5_KDB_REQUIRES_PRE_AUTH flag on the principal in the database.
@item @{-|+@}requires_hwauth
The ``+requires_hwauth'' flag requires the principal to preauthenticate
using a hardware device before being allowed to kinit.
``-requires_hwauth'' clears this flag. In effect, ``+requires_hwauth''
sets the KRB5_KDB_REQUIRES_HW_AUTH flag on the principal in the
database.
@item @{-|+@}allow_svr
The ``-allow_svr'' flag prohibits the issuance of service tickets for
this principal. ``+allow_svr'' clears this flag. In effect,
``-allow_svr'' sets the @* KRB5_KDB_DISALLOW_SVR flag on the principal
in the database.
@item @{-|+@}allow_tgs_req
The ``-allow_tgs_req'' option specifies that a Ticket-Granting Service
(TGS) request for a service ticket for this principal is not permitted.
You will probably never need to use this option. ``+allow_tgs_req''
clears this flag. The default is ``+allow_tgs_req''. In effect,
``-allow_tgs_req'' sets the KRB5_KDB_DISALLOW_TGT_BASED flag on the
principal in the database.
@item @{-|+@}allow_tix
The ``-allow_tix'' option forbids the issuance of any tickets for this
principal. ``+allow_tix'' clears this flag. The default is
``+allow_tix''. In effect, ``-allow_tix'' sets the @*
KRB5_KDB_DISALLOW_ALL_TIX flag on the principal in the database.
@item @{-|+@}needchange
The ``+needchange'' option sets a flag in attributes field to force a
password change; ``-needchange'' clears it. The default is
``-needchange''. In effect, ``+needchange'' sets the
KRB5_KDB_REQUIRES_PWCHANGE flag on the principal in the database.
@item @{-|+@}password_changing_service
The ``+password_changing_service'' option sets a flag in the attributes
field marking this principal as a password change service. (Again, you
will probably never need to use this option.)
``-password_changing_service'' clears the flag. The default is
``-password_changing_service''. In effect, the
``+password_changing_service'' option sets the KRB5_KDB_PWCHANGE_SERVICE
flag on the principal in the database.
@item -clearpolicy @i{policyname}
Removes the policy @i{policyname} from the principal
(@code{modify_principal} only).
@item -randkey
Sets the key for the principal to a random value (@code{add_principal}
only). @value{COMPANY} recommends using this option for host keys.
@item -pw @i{password}
Sets the key of the principal to the specified string and does not
prompt for a password (@code{add_principal} only). @value{COMPANY} does
not recommend using this option.
@item -e @i{enc:salt...}
Uses the specified list of enctype-salttype pairs for setting the key of
the principal. The quotes are necessary if there are multiple
enctype-salttype pairs. This will not function against kadmin daemons
earlier than krb5-1.2.
@end table
If you want to just use the default values, all you need to do is:
@smallexample
@group
@b{kadmin:} addprinc @value{RANDOMUSER1}
@b{WARNING: no policy specified for "@value{RANDOMUSER1}@@@value{PRIMARYREALM}";
defaulting to no policy.}
@iftex
@b{Enter password for principal @value{RANDOMUSER1}@@@value{PRIMARYREALM}:} @i{@doubleleftarrow{} Type the password.}
@b{Re-enter password for principal @value{RANDOMUSER1}@@@value{PRIMARYREALM}:} @i{@doubleleftarrow{} Type it again.}
@end iftex
@ifinfo
@b{Enter password for principal @value{RANDOMUSER1}@@@value{PRIMARYREALM}:} @i{<= Type the password.}
@b{Re-enter password for principal @value{RANDOMUSER1}@@@value{PRIMARYREALM}:} @i{<=Type it again.}
@end ifinfo
@b{Principal "@value{RANDOMUSER1}@@@value{PRIMARYREALM}" created.
kadmin:}
@end group
@end smallexample
If, on the other hand, you want to set up an account that expires on
January 1, 2000, that uses a policy called ``stduser'', with a temporary
password (which you want the user to change immediately), you would type
the following. (Note: each line beginning with @result{} is a
continuation of the previous line.)
@smallexample
@group
@b{kadmin:} addprinc @value{RANDOMUSER2} -expire "1/1/2000 12:01am EST" -policy stduser
@result{} +needchange
@iftex
@b{Enter password for principal @value{RANDOMUSER2}@@@value{PRIMARYREALM}:} @i{@doubleleftarrow{} Type the password.}
@b{Re-enter password for principal
@value{RANDOMUSER2}@@@value{PRIMARYREALM}:} @i{@doubleleftarrow{} Type it again.}
@end iftex
@ifinfo
@b{Enter password for principal @value{RANDOMUSER2}@@@value{PRIMARYREALM}:} @i{<= Type the password.}
@b{Re-enter password for principal
@value{RANDOMUSER2}@@@value{PRIMARYREALM}:} @i{<= Type it again.}
@end ifinfo
@b{Principal "@value{RANDOMUSER2}@@@value{PRIMARYREALM}" created.
kadmin:}
@end group
@end smallexample
If you will need cross-realm authentication, you need to add principals
for the other realm's TGT to each realm. For example, if you need to do
cross-realm authentication between the realms @value{PRIMARYREALM} and
@value{SECONDREALM}, you would need to add the principals @*
@samp{krbtgt/@value{SECONDREALM}@@@value{PRIMARYREALM}} and
@samp{krbtgt/@value{PRIMARYREALM}@@@value{SECONDREALM}} to both
databases. You need to be sure the passwords and the key version
numbers (kvno) are the same in both databases. This may require
explicitly setting the kvno with the @samp{-kvno} option.
@node Deleting Principals, Changing Passwords, Adding or Modifying Principals, Principals
@subsection Deleting Principals
To delete a principal, use the kadmin @code{delete_principal} command,
which requires the ``delete'' administrative privilege. The syntax is:
@smallexample
@b{delete_principal} [@b{-force}] @i{principal}
@end smallexample
@noindent @code{delete_principal} has the alias @code{delprinc}. The
@code{-force} option causes @code{delete_principal} not to ask if you're
sure. For example:
@smallexample
@group
@b{kadmin:} delprinc @value{RANDOMUSER1}
@b{Are you sure you want to delete the principal
"@value{RANDOMUSER1}@@@value{PRIMARYREALM}"? (yes/no):} yes
@b{Principal "@value{RANDOMUSER1}@@@value{PRIMARYREALM}" deleted.
Make sure that you have removed this principal from
all ACLs before reusing.
kadmin:}
@end group
@end smallexample
@node Changing Passwords, , Deleting Principals, Principals
@subsection Changing Passwords
To change a principal's password use the kadmin @code{change_password}
command, which requires the ``modify'' administrative privilege (unless
the principal is changing his/her own password). The syntax is:
@smallexample
@b{change_password} [@i{options}] @i{principal}
@end smallexample
@noindent The @code{change_password} option has the alias @code{cpw}.
@code{change_password} takes the following options:
@table @b
@item @b{-salt} @i{salttype}
Uses the specified salt for generating the key. Salt types are the same
as for the @code{add_principal} command (@pxref{Adding or Modifying
Principals}).
@item -randkey
Sets the key of the principal to a random value.
@item @b{-pw} @i{password}
Sets the password to the string @i{password}. @value{COMPANY} does not
recommend using this option.
@item @b{-e} @i{"enc:salt..."}
Uses the specified list of enctype-salttype pairs for setting the key of
the principal. The quotes are necessary if there are multiple
enctype-salttype pairs. This will not function against kadmin daemons
earlier than krb5-1.2.
@end table
For example:
@smallexample
@group
@b{kadmin:} cpw @value{RANDOMUSER2}
@iftex
@b{Enter password for principal @value{RANDOMUSER2}@@@value{PRIMARYREALM}:} @i{@doubleleftarrow{} Type the new password.}
@b{Re-enter password for principal @value{RANDOMUSER2}@@@value{PRIMARYREALM}:} @i{@doubleleftarrow{} Type it again.}
@end iftex
@ifinfo
@b{Enter password for principal @value{RANDOMUSER2}@@@value{PRIMARYREALM}:} @i{<= Type the new password.}
@b{Re-enter password for principal @value{RANDOMUSER2}@@@value{PRIMARYREALM}:} @i{<= Type it again.}
@end ifinfo
@b{Password for @value{RANDOMUSER2}@@@value{PRIMARYREALM} changed.
kadmin:}
@end group
@end smallexample
Note that @code{change_password} will not let you change the password to
one that is in the principal's password history.
@node Policies, Dumping a Kerberos Database to a File, Principals, Administrating Kerberos Database Entries
@section Policies
A policy is a set of rules governing passwords. Policies can dictate
minimum and maximum password lifetimes, minimum number of characters and
character classes a password must contain, and the number of old
passwords kept in the database.
@menu
* Retrieving Policies::
* Retrieving the List of Policies::
* Adding or Modifying Policies::
* Deleting Policies::
@end menu
@node Retrieving Policies, Retrieving the List of Policies, Policies, Policies
@subsection Retrieving Policies
To retrieve a policy, use the kadmin @code{get_policy} command, which
requires the ``inquire'' administrative privilege. The syntax is:
@smallexample
@b{get_policy} [@b{-terse}] @i{policy}
@end smallexample
The @code{get_policy} command has the alias @code{getpol}. For example:
@smallexample
@group
@b{kadmin:} get_policy admin
@b{Policy: admin
Maximum password life: 180 days 00:00:00
Minimum password life: 00:00:00
Minimum password length: 6
Minimum number of password character classes: 2
Number of old keys kept: 5
Reference count: 17
kadmin:}
@end group
@end smallexample
@noindent The @dfn{reference count} is the number of principals using
that policy.
The @code{get_policy} command has a @code{-terse} option, which lists
each field as a quoted, tab-separated string. For example:
@smallexample
@group
@b{kadmin:} get_policy -terse admin
@b{admin 15552000 0 6 2 5 17
kadmin:}
@end group
@end smallexample
@node Retrieving the List of Policies, Adding or Modifying Policies, Retrieving Policies, Policies
@subsection Retrieving the List of Policies
You can retrieve the list of policies with the kadmin
@code{list_policies} command, which requires the ``list'' privilege. The
syntax is:
@smallexample
@b{list_policies} [@i{expression}]
@end smallexample
@noindent where @i{expression} is a shell-style glob expression that can
contain the characters *, ?, and []. All policy names matching the
expression are displayed. The @code{list_policies} command has the alias
@code{listpols}. For example:
@smallexample
@group
@b{kadmin:} listpols
@b{test-pol
dict-only
once-a-min
test-pol-nopw}
@b{kadmin:} listpols t*
@b{test-pol
test-pol-nopw
kadmin:}
@end group
@end smallexample
@node Adding or Modifying Policies, Deleting Policies, Retrieving the List of Policies, Policies
@subsection Adding or Modifying Policies
To add a new policy, use the kadmin @code{add_policy} command, which
requires the ``add'' administrative privilege. The syntax is:
@smallexample
@b{add_policy} [@i{options}] @i{policy_name}
@end smallexample
To modify attributes of a principal, use the kadmin @code{modify_policy}
command, which requires the ``modify'' administrative privilege. The
syntax is:
@smallexample
@b{modify_policy} [@i{options}] @i{policy_name}
@end smallexample
@noindent @code{add_policy} has the alias @code{addpol}.
@code{modify_poilcy} has the alias @code{modpol}.
The @code{add_policy} and @code{modify_policy} commands take the
following switches:
@table @b
@item -maxlife @i{time}
Sets the maximum lifetime of a password to @i{time}.
@item -minlife @i{time}
Sets the minimum lifetime of a password to @i{time}.
@item -minlength @i{length}
Sets the minimum length of a password to @i{length} characters.
@item -minclasses @i{number}
Requires at least @i{number} of character classes in a password.
@item -history @i{number}
Sets the number of past keys kept for a principal to @i{number}.
@end table
@c **** An example here would be nice. ****
@node Deleting Policies, , Adding or Modifying Policies, Policies
@subsection Deleting Policies
To delete a policy, use the @code{kadmin} @code{delete_policy} command,
which requires the ``delete'' administrative privilege. The syntax is:
@smallexample
@b{delete_policy} @i{policy_name}
@end smallexample
@noindent The @code{delete_policy} command has the alias @code{delpol}.
It prompts for confirmation before deletion.
For example:
@smallexample
@group
@b{kadmin:} delete_policy guests
@b{Are you sure you want to delete the policy "guests"?
(yes/no):} yes
@b{Policy "guests" deleted.
kadmin:}
@end group
@end smallexample
Note that you must cancel the policy from all principals before deleting
it. The @code{delete_policy} command will fail if it is in use by any
principals.
@node Dumping a Kerberos Database to a File, Restoring a Kerberos Database from a Dump File, Policies, Administrating Kerberos Database Entries
@section Dumping a Kerberos Database to a File
To dump a Kerberos database into a file, use the @code{kdb5_util}
@code{dump} command on one of the KDCs. The syntax is:
@smallexample
@b{kdb5_util dump} [@b{-old}] [@b{-b6}] [@b{-b7}] [@b{-ov}] [@b{-verbose}]
[@i{filename} [@i{principals...}]]
@end smallexample
The @code{kdb5_util dump} command takes the following options:
@table @b
@itemx -old
causes the dump to be in the Kerberos 5 Beta 5 and earlier dump format
(``kdb5_edit load_dump version 2.0'').
@itemx -b6
causes the dump to be in the Kerberos 5 Beta 6 format (``kdb5_edit
load_dump version 3.0'').
@itemx -b7
causes the dump to be in the Kerberos 5 Beta 7 format (``kdb5_util
load_dump version 4''). This was the dump format produced on releases
prior to 1.2.2.
@itemx -ov
causes the dump to be in ovsec_adm_export format.
@itemx -verbose
causes the name of each principal and policy to be printed as it is
dumped.
@end table
For example:
@smallexample
@group
@b{shell%} kdb5_util dump dumpfile
@b{shell%}
@end group
@end smallexample
@smallexample
@group
@b{shell%} kbd5_util dump -verbose dumpfile
@b{kadmin/admin@@@value{PRIMARYREALM}
krbtgt/@value{PRIMARYREALM}@@@value{PRIMARYREALM}
kadmin/history@@@value{PRIMARYREALM}
K/M@@@value{PRIMARYREALM}
kadmin/changepw@@@value{PRIMARYREALM}
shell%}
@end group
@end smallexample
@noindent
If you specify which principals to dump, you must use the full
principal, as in the following example. (The line beginning with
@result{} is a continuation of the previous line.):
@smallexample
@group
@b{shell%} kdb5_util dump -verbose dumpfile K/M@@@value{PRIMARYREALM}
@result{} kadmin/admin@@@value{PRIMARYREALM}
@b{kadmin/admin@@@value{PRIMARYREALM}
K/M@@@value{PRIMARYREALM}
shell%}
@end group
@end smallexample
@noindent
Otherwise, the principals will not match those in the database and will
not be dumped:
@smallexample
@group
@b{shell%} kdb5_util dump -verbose dumpfile K/M kadmin/admin
@b{shell%}
@end group
@end smallexample
@noindent
If you do not specify a dump file, @code{kdb5_util} will dump the
database to the standard output.
@node Restoring a Kerberos Database from a Dump File, Creating a Stash File, Dumping a Kerberos Database to a File, Administrating Kerberos Database Entries
@section Restoring a Kerberos Database from a Dump File
To restore a Kerberos database dump from a file, use the
@code{kdb5_util} @code{load} command on one of the KDCs. The syntax
is:
@smallexample
@b{kdb5_util load} [@b{-old}] [@b{-b6}] [@b{-b7}] [@b{-ov}] [@b{-verbose}]
[@b{-update}] @i{dumpfilename} @i{dbname} [@i{admin_dbname}]
@end smallexample
The @code{kdb5_util load} command takes the following options:
@table @b
@itemx -old
requires the dump to be in the Kerberos 5 Beta 5 and earlier dump format
(``kdb5_edit load_dump version 2.0'').
@itemx -b6
requires the dump to be in the Kerberos 5 Beta 6 format (``kdb5_edit
load_dump version 3.0'').
@itemx -b7
requires the dump to be in the Kerberos 5 Beta 7 format (``kdb5_util
load_dump version 4'').
@itemx -ov
requires the dump to be in ovsec_adm_export format.
@itemx -verbose
causes the name of each principal and policy to be printed as it is
dumped.
@itemx -update
causes records from the dump file to be updated in or added to the
existing database.
@end table
For example:
@smallexample
@group
@b{shell%} kdb5_util load dumpfile principal
@b{shell%}
@end group
@end smallexample
@smallexample
@group
@b{shell%} kdb5_util load -update dumpfile principal
@b{shell%}
@end group
@end smallexample
@noindent
If the database file exists, and the @b{-update} flag was not given,
@code{kdb5_util} will overwrite the existing database.
@node Creating a Stash File, Creating and Destroying a Kerberos Database, Restoring a Kerberos Database from a Dump File, Administrating Kerberos Database Entries
@section Creating a Stash File
A stash file allows a KDC to authenticate itself to the database
utilities, such as @code{kadmin}, @code{kadmind}, @code{krb5kdc}, and
@code{kdb5_util}.
To create a stash file, use the @code{kdb5_util} @code{stash} command.
The syntax is:
@smallexample
@b{kdb5_util stash} [@b{-f} @i{keyfile}]
@end smallexample
For example:
@smallexample
@group
@b{shell%} kdb5_util stash
@b{kdb5_util: Cannot find/read stored master key while reading master key
kdb5_util: Warning: proceeding without master key}
@iftex
@b{Enter KDC database master key:} @i{@doubleleftarrow{} Type the KDC database master password.}
@end iftex
@ifinfo
@b{Enter KDC database master key:} @i{<= Type the KDC database master password.}
@end ifinfo
@b{shell%}
@end group
@end smallexample
@noindent
If you do not specify a stash file, @code{kdb5_util} will stash the key
in the file specified in your @code{kdc.conf} file.
@node Creating and Destroying a Kerberos Database, , Creating a Stash File, Administrating Kerberos Database Entries
@section Creating and Destroying a Kerberos Database
If you need to create a new Kerberos database, use the @code{kdb5_util}
@code{create} command. The syntax is:
@smallexample
@b{kdb5_util create} [@b{-s}]
@end smallexample
If you specify the @samp{-s} option, @code{kdb5_util} will stash a copy
of the master key in a stash file. (@xref{Creating a Stash File}.) For
example:
@smallexample
@group
@b{shell%} @value{ROOTDIR}/sbin/kdb5_util -r @value{PRIMARYREALM} create -s
@b{kdb5_util: No such file or directory while setting active database to
@result{} '@value{ROOTDIR}/var/krb5kdc/principal'
Initializing database '@value{ROOTDIR}/var/krb5kdc/principal' for
@result{} realm '@value{PRIMARYREALM}',
master key name 'K/M@@@value{PRIMARYREALM}'
You will be prompted for the database Master Password.
It is important that you NOT FORGET this password.}
@iftex
@b{Enter KDC database master key:} @i{@doubleleftarrow{} Type the master password.}
@b{Re-enter KDC database master key to verify:} @i{@doubleleftarrow{} Type it again.}
@end iftex
@ifinfo
@b{Enter KDC database master key:} @i{<= Type the master password.}
@b{Re-enter KDC database master key to verify:} @i{<= Type it again.}
@end ifinfo
@b{shell%}
@end group
@end smallexample
@ignore
@c @node The KDC Logs, , Creating and Destroying a Kerberos Database, Administrating Kerberos Database Entries
@c @section The KDC Logs
This will have to wait until the next release. *sigh*
@end ignore
@node Application Servers, Backups of Secure Hosts, Administrating Kerberos Database Entries, Top
@chapter Application Servers
If you need to install the @value{PRODUCT} programs on an application
server, please refer to the @value{PRODUCT} Installation Guide. Once
you have installed the software, you need to add that host to the
Kerberos database (@pxref{Adding or Modifying Principals}), and generate
a @dfn{keytab} for that host, that contains the host's key. You also
need to make sure the host's clock is within your maximum clock skew of
the KDCs.
@menu
* Keytabs::
* Clock Skew::
* Getting DNS Information Correct::
* Configuring Your Firewall to Work With Kerberos V5::
@end menu
@node Keytabs, Clock Skew, Application Servers, Application Servers
@section Keytabs
A @dfn{keytab} is a host's copy of its own keylist, which is analogous
to a user's password. An application server that needs to authenticate
itself to the KDC has to have a keytab that contains its own principal
and key. Just as it is important for users to protect their passwords,
it is equally important for hosts to protect their keytabs. You should
always store keytab files on local disk, and make them readable only by
root, and you should never send a keytab file over a network in the
clear. Ideally, you should run the @code{kadmin} command to extract a
keytab on the host on which the keytab is to reside.
@menu
* Adding Principals to Keytabs::
* Removing Principals from Keytabs::
@end menu
@node Adding Principals to Keytabs, Removing Principals from Keytabs, Keytabs, Keytabs
@subsection Adding Principals to Keytabs
To generate a keytab, or to add a principal to an existing keytab, use
the @code{ktadd} command from @code{kadmin}, which requires the
``inquire'' administrative privilege. (If you use the @b{-glob}
@i{princ_exp} option, it also requires the ``list'' administrative
privilege.) The syntax is:
@smallexample
@b{ktadd} [@b{-k} @i{keytab}] [@b{-q}] [@i{principal} | @b{-glob} @i{princ_exp}] [@i{@dots{}}]
@end smallexample
The @code{ktadd} command takes the following switches:
@table @b
@item -k @i{keytab}
use @i{keytab} as the keytab file. Otherwise, @code{ktadd} will use the
default keytab file (@code{/etc/krb5.keytab}).
@item @b{-e} @i{"enc:salt..."}
Uses the specified list of enctype-salttype pairs for setting the key of
the principal. The quotes are necessary if there are multiple
enctype-salttype pairs. This will not function against kadmin daemons
earlier than krb5-1.2.
@item -q
run in quiet mode. This causes @code{ktadd} to display less verbose
information.
@item @i{principal} | -glob @i{principal expression}
add @i{principal}, or all principals matching @i{principal expression}
to the keytab. The rules for @i{principal expression} are the same as
for the kadmin @code{list_principals} (@pxref{Retrieving a List of
Principals}) command.
@end table
Here is a sample session, using configuration files that enable only
@samp{des-cbc-crc} encryption. (The line beginning with @result{} is a
continuation of the previous line.)
@smallexample
@group
@b{kadmin:} ktadd host/@value{RANDOMHOST1}.@value{PRIMARYDOMAIN}@@@value{PRIMARYREALM}
@b{kadmin: Entry for principal host/@value{RANDOMHOST1}.@value{PRIMARYDOMAIN}@@@value{PRIMARYREALM} with
kvno 2, encryption type DES-CBC-CRC added to keytab
WRFILE:/etc/krb5.keytab.
kadmin:}
@end group
@end smallexample
@smallexample
@group
@b{kadmin:} ktadd -k @value{ROOTDIR}/var/krb5kdc/kadmind.keytab
@result{} kadmin/admin kadmin/changepw
@b{kadmin: Entry for principal kadmin/admin@@@value{PRIMARYREALM} with
kvno 3, encryption type DES-CBC-CRC added to keytab
WRFILE:@value{ROOTDIR}/var/krb5kdc/kadmind.keytab.
kadmin:}
@end group
@end smallexample
@node Removing Principals from Keytabs, , Adding Principals to Keytabs, Keytabs
@subsection Removing Principals from Keytabs
To remove a principal to an existing keytab, use the kadmin
@code{ktremove} command. The syntax is:
@smallexample
@b{ktremove} [@b{-k} @i{keytab}] [@b{-q}] @i{principal} [@i{kvno} | @b{all} | @b{old}]
@end smallexample
The @code{ktremove} command takes the following switches:
@table @b
@item -k @i{keytab}
use @i{keytab} as the keytab file. Otherwise, @code{ktremove} will use
the default keytab file (@code{/etc/krb5.keytab}).
@item -q
run in quiet mode. This causes @code{ktremove} to display less verbose
information.
@item @i{principal}
the principal to remove from the keytab. (Required.)
@item @i{kvno}
remove all entries for the specified principal whose Key Version Numbers
match @i{kvno}.
@item all
remove all entries for the specified principal
@item old
remove all entries for the specified principal except those with the
highest kvno.
@end table
For example:
@smallexample
@group
@b{kadmin:} ktremove -k @value{ROOTDIR}/var/krb5kdc/kadmind.keytab kadmin/admin
@b{kadmin: Entry for principal kadmin/admin with kvno 3 removed
from keytab WRFILE:@value{ROOTDIR}/var/krb5kdc/kadmind.keytab.
kadmin:}
@end group
@end smallexample
@node Clock Skew, Getting DNS Information Correct, Keytabs, Application Servers
@section Clock Skew
In order to prevent intruders from resetting their system clocks in
order to continue to use expired tickets, @value{PRODUCT} is set up to
reject ticket requests from any host whose clock is not within the
specified maximum clock skew of the KDC (as specified in the
@code{kdc.conf} file). Similarly, hosts are configured to reject
responses from any KDC whose clock is not within the specified maximum
clock skew of the host (as specified in the @code{krb5.conf} file). The
default value for maximum clock skew is 300 seconds (five minutes).
@value{COMPANY} suggests that you add a line to client machines'
@code{/etc/rc} files to synchronize the machine's clock to your KDC at
boot time. On UNIX hosts, assuming you had a kdc called
@code{@value{KDCSERVER}} in your realm, this would be:
@smallexample
gettime -s @value{KDCSERVER}
@end smallexample
If the host is not likely to be rebooted frequently, you may also want
to set up a cron job that adjusts the time on a regular basis.
@node Getting DNS Information Correct, Configuring Your Firewall to Work With Kerberos V5, Clock Skew, Application Servers
@section Getting DNS Information Correct
Several aspects of Kerberos rely on name service. In order for Kerberos
to provide its high level of security, it is less forgiving of name
service problems than some other parts of your network. It is important
that your Domain Name System (DNS) entries and your hosts have the
correct information.
Each host's canonical name must be the fully-qualified host name
(including the domain), and each host's IP address must reverse-resolve
to the canonical name.
Other than the @code{localhost} entry, make all entries in each
machine's @code{/etc/hosts} file in the following form:
@smallexample
IP address fully-qualified hostname aliases
@end smallexample
Here is a sample @code{/etc/hosts} file:
@smallexample
@group
# this is a comment
127.0.0.1 localhost localhost@@@value{PRIMARYDOMAIN}
@value{RANDOMHOST1IP} @value{RANDOMHOST1}.@value{PRIMARYDOMAIN} trillium wake-robin
@end group
@end smallexample
Additionally, on Solaris machines, you need to be sure the ``hosts''
entry in the file @* @code{/etc/nsswitch.conf} includes the source
``dns'' as well as ``file''.
Finally, each host's keytab file must include a host/key pair for the
host's canonical name. You can list the keys in a keytab file by
issuing the command @code{klist -k}. For example:
@smallexample
@group
viola# klist -k
Keytab name: /etc/krb5.keytab
KVNO Principal
---- ------------------------------------------------------------
1 host/@value{RANDOMHOST1}.@value{PRIMARYDOMAIN}@@@value{PRIMARYREALM}
@end group
@end smallexample
If you telnet to the host with a fresh credentials cache (ticket file),
and then @code{klist}, the host's service principal should be
@i{host/fully-qualified-hostname@@REALM_NAME}.
@node Configuring Your Firewall to Work With Kerberos V5, , Getting DNS Information Correct, Application Servers
@section Configuring Your Firewall to Work With @value{PRODUCT}
If you need off-site users to be able to get Kerberos tickets in your
realm, they must be able to get to your KDC. This requires either that
you have a slave KDC outside your firewall, or you configure your
firewall to allow UDP requests into to at least one of your KDCs, on
whichever port the KDC is running. (The default is port 88; other ports
may be specified in the KDC's kdc.conf file.) Similarly, if you need
off-site users to be able to change their passwords in your realm, they
must be able to get to your Kerberos admin server. The default port for
the admin server is 749.
If your on-site users inside your firewall will need to get to KDCs in
other realms, you will also need to configure your firewall to allow
outgoing TCP and UDP requests to port 88. Additionally, if they will
need to get to any Kerberos V4 KDCs, you may also need to allow TCP and
UDP requests to port 750. If your on-site users inside your firewall
will need to get to Kerberos admin servers in other realms, you will
also need to allow outgoing TCP and UDP requests to port 749.
If any of your KDCs is outside your firewall, you will need to allow
@code{kprop} requests to get through to the remote KDC. @code{Kprop}
uses the krb5_prop service on port 754 (tcp).
If you need your off-site users to have access to machines inside your
firewall, you need to allow TCP connections from their off-site hosts on
the appropriate ports for the programs they will be using. The
following lines from @code{/etc/services} show the default port numbers
for the @value{PRODUCT} programs:
@smallexample
@group
ftp 21/tcp # Kerberos ftp and telnet use the
telnet 23/tcp # default ports
kerberos 88/udp kdc # Kerberos V5 KDC
kerberos 88/tcp kdc # Kerberos V5 KDC
klogin 543/tcp # Kerberos authenticated rlogin
kshell 544/tcp cmd # and remote shell
kerberos-adm 749/tcp # Kerberos 5 admin/changepw
kerberos-adm 749/udp # Kerberos 5 admin/changepw
krb5_prop 754/tcp # Kerberos slave propagation
@c kpop 1109/tcp # Pop with Kerberos
eklogin 2105/tcp # Kerberos auth. & encrypted rlogin
krb524 4444/tcp # Kerberos 5 to 4 ticket translator
@end group
@end smallexample
By default, @value{PRODUCT} @code{telnet} and @code{ftp} use the same
ports as the standard @code{telnet} and @code{ftp} programs, so if you
already allow telnet and ftp connections through your firewall, the
@value{PRODUCT} versions will get through as well. If you do not
already allow telnet and ftp connections through your firewall, but need
your users to be able to use @value{PRODUCT} telnet and ftp, you can
either allow ftp and telnet connections on the standard ports, or switch
these programs to non-default port numbers and allow ftp and telnet
connections on those ports to get through.
@value{PRODUCT} @code{rlogin} uses the @code{klogin} service, which by
default uses port 543. Encrypted @value{PRODUCT} rlogin uses uses the
@code{eklogin} service, which by default uses port 2105.
@value{PRODUCT} @code{rsh} uses the @code{kshell} service, which by
default uses port 544. However, the server must be able to make a TCP
connection from the kshell port to an arbitrary port on the client, so
if your users are to be able to use @code{rsh} from outside your
firewall, the server they connect to must be able to send outgoing
packets to arbitrary port numbers. Similarly, if your users need to run
@code{rsh} from inside your firewall to hosts outside your firewall, the
outside server needs to be able to connect to an arbitrary port on the
machine inside your firewall. Because @value{PRODUCT} @code{rcp} uses
@code{rsh}, the same issues apply. If you need to use @code{rsh} (or
@code{rcp}) through your firewall and are concerned with the security
implications of allowing connections to arbitrary ports, @value{COMPANY}
suggests that you have rules that specifically name these applications
and, if possible, list the allowed hosts.
A reasonably good cookbook for configuring firewalls is available by FTP
from @* @code{ftp.livingston.com}, in the location:
@code{/pub/firewall/firewall-1.1.ps.Z}. The book @cite{UNIX System
Security}, by David Curry, is also a good starting point.
@ignore
@c @node Enabling Users to Connect from Off-Site, , Configuring Your Firewall to Work With @value{PRODUCT}, Application Servers
@c @section Enabling Users to Connect from Off-Site
This will have to wait until the next release. *sigh*
@end ignore
@node Backups of Secure Hosts, Bug Reporting, Application Servers, Top
@chapter Backups of Secure Hosts
When you back up a secure host, you should exclude the host's keytab
file from the backup. If someone obtained a copy of the keytab from a
backup, that person could make any host masquerade as the host whose
keytab was compromised. This could be particularly dangerous if the
compromised keytab was from one of your KDCs. If the machine has a disk
crash and the keytab file is lost, it is easy to generate another keytab
file. (@xref{Adding Principals to Keytabs}.) If you are unable to
exclude particular files from backups, you should ensure that the
backups are kept as secure as the host's root password.
@menu
* Backing Up the Kerberos Database::
@end menu
@node Backing Up the Kerberos Database, , Backups of Secure Hosts, Backups of Secure Hosts
@section Backing Up the Kerberos Database
As with any file, it is possible that your Kerberos database could
become corrupted. If this happens on one of the slave KDCs, you might
never notice, since the next automatic propagation of the database would
install a fresh copy. However, if it happens to the master KDC, the
corrupted database would be propagated to all of the slaves during the
next propagation. For this reason, @value{COMPANY} recommends that you
back up your Kerberos database regularly. Because the master KDC is
continuously dumping the database to a file in order to propagate it to
the slave KDCs, it is a simple matter to have a cron job periodically
copy the dump file to a secure machine elsewhere on your network. (Of
course, it is important to make the host where these backups are stored
as secure as your KDCs, and to encrypt its transmission across your
network.) Then if your database becomes corrupted, you can load the
most recent dump onto the master KDC. (@xref{Restoring a Kerberos
Database from a Dump File}.)
@node Bug Reporting, Appendix, Backups of Secure Hosts, Top
@chapter Bug Reporting
@include send-pr.texinfo
@node Appendix, , Bug Reporting, Top
@appendix Appendix
@menu
* Errors::
* kadmin Time Zones::
@end menu
@node Errors, kadmin Time Zones, Appendix, Appendix
@appendixsec Kerberos Error Messages
@menu
* Kerberos V5 Library Error Codes::
* Kerberos V5 Database Library Error Codes::
* Kerberos V5 Magic Numbers Error Codes::
* ASN.1 Error Codes::
* GSSAPI Error Codes::
@end menu
@node Kerberos V5 Library Error Codes, Kerberos V5 Database Library Error Codes, Errors, Errors
@appendixsubsec Kerberos V5 Library Error Codes
This is the Kerberos v5 library error code table. Protocol error codes
are @* ERROR_TABLE_BASE_krb5 + the protocol error code number; other
error codes start at ERROR_TABLE_BASE_krb5 + 128.
@c error table numbering starts at 0
@enumerate 0
@item
KRB5KDC_ERR_NONE: No error
@item
KRB5KDC_ERR_NAME_EXP: Client's entry in database has expired
@item
KRB5KDC_ERR_SERVICE_EXP: Server's entry in database has expired
@item
KRB5KDC_ERR_BAD_PVNO: Requested protocol version not supported
@item
KRB5KDC_ERR_C_OLD_MAST_KVNO: Client's key is encrypted in an old master
key
@item
KRB5KDC_ERR_S_OLD_MAST_KVNO: Server's key is encrypted in an old master
key
@item
KRB5KDC_ERR_C_PRINCIPAL_UNKNOWN: Client not found in Kerberos database
@item
KRB5KDC_ERR_S_PRINCIPAL_UNKNOWN: Server not found in Kerberos database
@item
KRB5KDC_ERR_PRINCIPAL_NOT_UNIQUE: Principal has multiple entries in
Kerberos database
@item
KRB5KDC_ERR_NULL_KEY: Client or server has a null key
@item
KRB5KDC_ERR_CANNOT_POSTDATE: Ticket is ineligible for postdating
@item
KRB5KDC_ERR_NEVER_VALID: Requested effective lifetime is negative or
too short
@item
KRB5KDC_ERR_POLICY: KDC policy rejects request
@item
KRB5KDC_ERR_BADOPTION: KDC can't fulfill requested option
@item
KRB5KDC_ERR_ETYPE_NOSUPP: KDC has no support for encryption type
@item
KRB5KDC_ERR_SUMTYPE_NOSUPP: KDC has no support for checksum type
@item
KRB5KDC_ERR_PADATA_TYPE_NOSUPP: KDC has no support for padata type
@item
KRB5KDC_ERR_TRTYPE_NOSUPP: KDC has no support for transited type
@item
KRB5KDC_ERR_CLIENT_REVOKED: Clients credentials have been revoked
@item
KRB5KDC_ERR_SERVICE_REVOKED: Credentials for server have been revoked
@item
KRB5KDC_ERR_TGT_REVOKED: TGT has been revoked
@item
KRB5KDC_ERR_CLIENT_NOTYET: Client not yet valid - try again later
@item
KRB5KDC_ERR_SERVICE_NOTYET: Server not yet valid - try again later
@item
KRB5KDC_ERR_KEY_EXP: Password has expired
@item
KRB5KDC_ERR_PREAUTH_FAILED: Preauthentication failed
@item
@iftex
KRB5KDC_ERR_PREAUTH_REQUIRED: Additional pre-auth@-en@-ti@-ca@-tion required
@end iftex
@ifinfo
KRB5KDC_ERR_PREAUTH_REQUIRED: Additional preauthentication required
@end ifinfo
@item
KRB5KDC_ERR_SERVER_NOMATCH: Requested server and ticket don't match
@item
KRB5PLACEHOLD_27: KRB5 error code 27
@item
KRB5PLACEHOLD_28: KRB5 error code 28
@item
KRB5PLACEHOLD_29: KRB5 error code 29
@item
KRB5PLACEHOLD_30: KRB5 error code 30
@item
KRB5KRB_AP_ERR_BAD_INTEGRITY: Decrypt integrity check failed
@item
KRB5KRB_AP_ERR_TKT_EXPIRED: Ticket expired
@item
KRB5KRB_AP_ERR_TKT_NYV: Ticket not yet valid
@item
KRB5KRB_AP_ERR_REPEAT: Request is a replay
@item
KRB5KRB_AP_ERR_NOT_US: The ticket isn't for us
@item
KRB5KRB_AP_ERR_BADMATCH: Ticket/authenticator don't match
@item
KRB5KRB_AP_ERR_SKEW: Clock skew too great
@item
KRB5KRB_AP_ERR_BADADDR: Incorrect net address
@item
KRB5KRB_AP_ERR_BADVERSION: Protocol version mismatch
@item
KRB5KRB_AP_ERR_MSG_TYPE: Invalid message type
@item
KRB5KRB_AP_ERR_MODIFIED: Message stream modified
@item
KRB5KRB_AP_ERR_BADORDER: Message out of order
@item
KRB5KRB_AP_ERR_ILL_CR_TKT: Illegal cross-realm ticket
@item
KRB5KRB_AP_ERR_BADKEYVER: Key version is not available
@item
KRB5KRB_AP_ERR_NOKEY: Service key not available
@item
KRB5KRB_AP_ERR_MUT_FAIL: Mutual authentication failed
@item
KRB5KRB_AP_ERR_BADDIRECTION: Incorrect message direction
@item
KRB5KRB_AP_ERR_METHOD: Alternative authentication method required
@item
KRB5KRB_AP_ERR_BADSEQ: Incorrect sequence number in message
@item
KRB5KRB_AP_ERR_INAPP_CKSUM: Inappropriate type of checksum in message
@item
KRB5PLACEHOLD_51: KRB5 error code 51
@item
KRB5PLACEHOLD_52: KRB5 error code 52
@item
KRB5PLACEHOLD_53: KRB5 error code 53
@item
KRB5PLACEHOLD_54: KRB5 error code 54
@item
KRB5PLACEHOLD_55: KRB5 error code 55
@item
KRB5PLACEHOLD_56: KRB5 error code 56
@item
KRB5PLACEHOLD_57: KRB5 error code 57
@item
KRB5PLACEHOLD_58: KRB5 error code 58
@item
KRB5PLACEHOLD_59: KRB5 error code 59
@item
KRB5KRB_ERR_GENERIC: Generic error (see e-text)
@item
KRB5KRB_ERR_FIELD_TOOLONG: Field is too long for this implementation
@item
KRB5PLACEHOLD_62: KRB5 error code 62
@item
KRB5PLACEHOLD_63: KRB5 error code 63
@item
KRB5PLACEHOLD_64: KRB5 error code 64
@item
KRB5PLACEHOLD_65: KRB5 error code 65
@item
KRB5PLACEHOLD_66: KRB5 error code 66
@item
KRB5PLACEHOLD_67: KRB5 error code 67
@item
KRB5PLACEHOLD_68: KRB5 error code 68
@item
KRB5PLACEHOLD_69: KRB5 error code 69
@item
KRB5PLACEHOLD_70: KRB5 error code 70
@item
KRB5PLACEHOLD_71: KRB5 error code 71
@item
KRB5PLACEHOLD_72: KRB5 error code 72
@item
KRB5PLACEHOLD_73: KRB5 error code 73
@item
KRB5PLACEHOLD_74: KRB5 error code 74
@item
KRB5PLACEHOLD_75: KRB5 error code 75
@item
KRB5PLACEHOLD_76: KRB5 error code 76
@item
KRB5PLACEHOLD_77: KRB5 error code 77
@item
KRB5PLACEHOLD_78: KRB5 error code 78
@item
KRB5PLACEHOLD_79: KRB5 error code 79
@item
KRB5PLACEHOLD_80: KRB5 error code 80
@item
KRB5PLACEHOLD_81: KRB5 error code 81
@item
KRB5PLACEHOLD_82: KRB5 error code 82
@item
KRB5PLACEHOLD_83: KRB5 error code 83
@item
KRB5PLACEHOLD_84: KRB5 error code 84
@item
KRB5PLACEHOLD_85: KRB5 error code 85
@item
KRB5PLACEHOLD_86: KRB5 error code 86
@item
KRB5PLACEHOLD_87: KRB5 error code 87
@item
KRB5PLACEHOLD_88: KRB5 error code 88
@item
KRB5PLACEHOLD_89: KRB5 error code 89
@item
KRB5PLACEHOLD_90: KRB5 error code 90
@item
KRB5PLACEHOLD_91: KRB5 error code 91
@item
KRB5PLACEHOLD_92: KRB5 error code 92
@item
KRB5PLACEHOLD_93: KRB5 error code 93
@item
KRB5PLACEHOLD_94: KRB5 error code 94
@item
KRB5PLACEHOLD_95: KRB5 error code 95
@item
KRB5PLACEHOLD_96: KRB5 error code 96
@item
KRB5PLACEHOLD_97: KRB5 error code 97
@item
KRB5PLACEHOLD_98: KRB5 error code 98
@item
KRB5PLACEHOLD_99: KRB5 error code 99
@item
KRB5PLACEHOLD_100: KRB5 error code 100
@item
KRB5PLACEHOLD_101: KRB5 error code 101
@item
KRB5PLACEHOLD_102: KRB5 error code 102
@item
KRB5PLACEHOLD_103: KRB5 error code 103
@item
KRB5PLACEHOLD_104: KRB5 error code 104
@item
KRB5PLACEHOLD_105: KRB5 error code 105
@item
KRB5PLACEHOLD_106: KRB5 error code 106
@item
KRB5PLACEHOLD_107: KRB5 error code 107
@item
KRB5PLACEHOLD_108: KRB5 error code 108
@item
KRB5PLACEHOLD_109: KRB5 error code 109
@item
KRB5PLACEHOLD_110: KRB5 error code 110
@item
KRB5PLACEHOLD_111: KRB5 error code 111
@item
KRB5PLACEHOLD_112: KRB5 error code 112
@item
KRB5PLACEHOLD_113: KRB5 error code 113
@item
KRB5PLACEHOLD_114: KRB5 error code 114
@item
KRB5PLACEHOLD_115: KRB5 error code 115
@item
KRB5PLACEHOLD_116: KRB5 error code 116
@item
KRB5PLACEHOLD_117: KRB5 error code 117
@item
KRB5PLACEHOLD_118: KRB5 error code 118
@item
KRB5PLACEHOLD_119: KRB5 error code 119
@item
KRB5PLACEHOLD_120: KRB5 error code 120
@item
KRB5PLACEHOLD_121: KRB5 error code 121
@item
KRB5PLACEHOLD_122: KRB5 error code 122
@item
KRB5PLACEHOLD_123: KRB5 error code 123
@item
KRB5PLACEHOLD_124: KRB5 error code 124
@item
KRB5PLACEHOLD_125: KRB5 error code 125
@item
KRB5PLACEHOLD_126: KRB5 error code 126
@item
KRB5PLACEHOLD_127: KRB5 error code 127
@item
KRB5_ERR_RCSID: $Id$
@item
KRB5_LIBOS_BADLOCKFLAG: Invalid flag for file lock mode
@item
KRB5_LIBOS_CANTREADPWD: Cannot read password
@item
KRB5_LIBOS_BADPWDMATCH: Password mismatch
@item
KRB5_LIBOS_PWDINTR: Password read interrupted
@item
KRB5_PARSE_ILLCHAR: Illegal character in component name
@item
KRB5_PARSE_MALFORMED: Malformed representation of principal
@item
KRB5_CONFIG_CANTOPEN: Can't open/find configuration file
@item
KRB5_CONFIG_BADFORMAT: Improper format of configuration file
@item
KRB5_CONFIG_NOTENUFSPACE: Insufficient space to return complete
information
@item
KRB5_BADMSGTYPE: Invalid message type specified for encoding
@item
KRB5_CC_BADNAME: Credential cache name malformed
@item
KRB5_CC_UNKNOWN_TYPE: Unknown credential cache type
@item
KRB5_CC_NOTFOUND: Matching credential not found
@item
KRB5_CC_END: End of credential cache reached
@item
KRB5_NO_TKT_SUPPLIED: Request did not supply a ticket
@item
KRB5KRB_AP_WRONG_PRINC: Wrong principal in request
@item
KRB5KRB_AP_ERR_TKT_INVALID: Ticket has invalid flag set
@item
KRB5_PRINC_NOMATCH: Requested principal and ticket don't match
@item
KRB5_KDCREP_MODIFIED: KDC reply did not match expectations
@item
KRB5_KDCREP_SKEW: Clock skew too great in KDC reply
@item
KRB5_IN_TKT_REALM_MISMATCH: Client/server realm mismatch in initial
ticket request
@item
KRB5_PROG_ETYPE_NOSUPP: Program lacks support for encryption type
@item
KRB5_PROG_KEYTYPE_NOSUPP: Program lacks support for key type
@item
KRB5_WRONG_ETYPE: Requested encryption type not used in message
@item
KRB5_PROG_SUMTYPE_NOSUPP: Program lacks support for checksum type
@item
KRB5_REALM_UNKNOWN: Cannot find KDC for requested realm
@item
KRB5_SERVICE_UNKNOWN: Kerberos service unknown
@item
KRB5_KDC_UNREACH: Cannot contact any KDC for requested realm
@item
KRB5_NO_LOCALNAME: No local name found for principal name
@item
KRB5_MUTUAL_FAILED: Mutual authentication failed
@item
KRB5_RC_TYPE_EXISTS: Replay cache type is already registered
@item
KRB5_RC_MALLOC: No more memory to allocate (in replay cache code)
@item
KRB5_RC_TYPE_NOTFOUND: Replay cache type is unknown
@item
KRB5_RC_UNKNOWN: Generic unknown RC error
@item
KRB5_RC_REPLAY: Message is a replay
@item
KRB5_RC_IO: Replay I/O operation failed XXX
@item
KRB5_RC_NOIO: Replay cache type does not support non-volatile storage
@item
KRB5_RC_PARSE: Replay cache name parse/format error
@item
KRB5_RC_IO_EOF: End-of-file on replay cache I/O
@item
KRB5_RC_IO_MALLOC: No more memory to allocate (in replay cache I/O
code)
@item
KRB5_RC_IO_PERM: Permission denied in replay cache code
@item
KRB5_RC_IO_IO: I/O error in replay cache i/o code
@item
KRB5_RC_IO_UNKNOWN: Generic unknown RC/IO error
@item
KRB5_RC_IO_SPACE: Insufficient system space to store replay information
@item
KRB5_TRANS_CANTOPEN: Can't open/find realm translation file
@item
KRB5_TRANS_BADFORMAT: Improper format of realm translation file
@item
KRB5_LNAME_CANTOPEN: Can't open/find lname translation database
@item
KRB5_LNAME_NOTRANS: No translation available for requested principal
@item
KRB5_LNAME_BADFORMAT: Improper format of translation database entry
@item
KRB5_CRYPTO_INTERNAL: Cryptosystem internal error
@item
KRB5_KT_BADNAME: Key table name malformed
@item
KRB5_KT_UNKNOWN_TYPE: Unknown Key table type
@item
KRB5_KT_NOTFOUND: Key table entry not found
@item
KRB5_KT_END: End of key table reached
@item
KRB5_KT_NOWRITE: Cannot write to specified key table
@item
KRB5_KT_IOERR: Error writing to key table
@item
KRB5_NO_TKT_IN_RLM: Cannot find ticket for requested realm
@item
KRB5DES_BAD_KEYPAR: DES key has bad parity
@item
KRB5DES_WEAK_KEY: DES key is a weak key
@item
KRB5_BAD_ENCTYPE: Bad encryption type
@item
KRB5_BAD_KEYSIZE: Key size is incompatible with encryption type
@item
KRB5_BAD_MSIZE: Message size is incompatible with encryption type
@item
KRB5_CC_TYPE_EXISTS: Credentials cache type is already registered.
@item
KRB5_KT_TYPE_EXISTS: Key table type is already registered.
@item
KRB5_CC_IO: Credentials cache I/O operation failed XXX
@item
KRB5_FCC_PERM: Credentials cache file permissions incorrect
@item
KRB5_FCC_NOFILE: No credentials cache file found
@item
KRB5_FCC_INTERNAL: Internal file credentials cache error
@item
KRB5_CC_WRITE: Error writing to credentials cache file
@item
KRB5_CC_NOMEM: No more memory to allocate (in credentials cache code)
@item
KRB5_CC_FORMAT: Bad format in credentials cache
@item
KRB5_INVALID_FLAGS: Invalid KDC option combination (library internal
error) [for dual tgt library calls]
@item
KRB5_NO_2ND_TKT: Request missing second ticket [for dual tgt library
calls]
@item
KRB5_NOCREDS_SUPPLIED: No credentials supplied to library routine
@item
KRB5_SENDAUTH_BADAUTHVERS: Bad sendauth version was sent
@item
KRB5_SENDAUTH_BADAPPLVERS: Bad application version was sent (via
sendauth)
@item
KRB5_SENDAUTH_BADRESPONSE: Bad response (during sendauth exchange)
@item
KRB5_SENDAUTH_REJECTED: Server rejected authentication (during sendauth
exchange)
@item
KRB5_PREAUTH_BAD_TYPE: Unsupported preauthentication type
@item
KRB5_PREAUTH_NO_KEY: Required preauthentication key not supplied
@item
KRB5_PREAUTH_FAILED: Generic preauthentication failure
@item
KRB5_RCACHE_BADVNO: Unsupported replay cache format version number
@item
KRB5_CCACHE_BADVNO: Unsupported credentials cache format version number
@item
KRB5_KEYTAB_BADVNO: Unsupported key table format version number
@item
KRB5_PROG_ATYPE_NOSUPP: Program lacks support for address type
@item
KRB5_RC_REQUIRED: Message replay detection requires rcache parameter
@item
KRB5_ERR_BAD_HOSTNAME: Hostname cannot be canonicalized
@item
KRB5_ERR_HOST_REALM_UNKNOWN: Cannot determine realm for host
@item
KRB5_SNAME_UNSUPP_NAMETYPE: Conversion to service principal undefined
for name type
@item
KRB5KRB_AP_ERR_V4_REPLY: Initial Ticket response appears to be Version
4 error
@item
KRB5_REALM_CANT_RESOLVE: Cannot resolve KDC for requested realm
@item
KRB5_TKT_NOT_FORWARDABLE: Requesting ticket can't get forwardable
tickets
@item
KRB5_FWD_BAD_PRINCIPAL: Bad principal name while trying to forward
credentials
@item
KRB5_GET_IN_TKT_LOOP: Looping detected inside krb5_get_in_tkt
@item
KRB5_CONFIG_NODEFREALM: Configuration file does not specify default
realm
@item
KRB5_SAM_UNSUPPORTED: Bad SAM flags in obtain_sam_padata
@end enumerate
@node Kerberos V5 Database Library Error Codes, Kerberos V5 Magic Numbers Error Codes, Kerberos V5 Library Error Codes, Errors
@appendixsubsec Kerberos V5 Database Library Error Codes
This is the Kerberos v5 database library error code table.
@c error table numbering starts at 0
@enumerate 0
@item
KRB5_KDB_RCSID: $Id$
@item
KRB5_KDB_INUSE: Entry already exists in database
@item
KRB5_KDB_UK_SERROR: Database store error
@item
KRB5_KDB_UK_RERROR: Database read error
@item
KRB5_KDB_UNAUTH: Insufficient access to perform requested operation
@item
KRB5_KDB_NOENTRY: No such entry in the database
@item
KRB5_KDB_ILL_WILDCARD: Illegal use of wildcard
@item
KRB5_KDB_DB_INUSE: Database is locked or in use--try again later
@item
KRB5_KDB_DB_CHANGED: Database was modified during read
@item
KRB5_KDB_TRUNCATED_RECORD: Database record is incomplete or corrupted
@item
KRB5_KDB_RECURSIVELOCK: Attempt to lock database twice
@item
KRB5_KDB_NOTLOCKED: Attempt to unlock database when not locked
@item
KRB5_KDB_BADLOCKMODE: Invalid kdb lock mode
@item
KRB5_KDB_DBNOTINITED: Database has not been initialized
@item
KRB5_KDB_DBINITED: Database has already been initialized
@item
KRB5_KDB_ILLDIRECTION: Bad direction for converting keys
@item
KRB5_KDB_NOMASTERKEY: Cannot find master key record in database
@item
KRB5_KDB_BADMASTERKEY: Master key does not match database
@item
KRB5_KDB_INVALIDKEYSIZE: Key size in database is invalid
@item
KRB5_KDB_CANTREAD_STORED: Cannot find/read stored master key
@item
KRB5_KDB_BADSTORED_MKEY: Stored master key is corrupted
@item
KRB5_KDB_CANTLOCK_DB: Insufficient access to lock database
@item
KRB5_KDB_DB_CORRUPT: Database format error
@item
KRB5_KDB_BAD_VERSION: Unsupported version in database entry
@item
KRB5_KDB_BAD_SALTTYPE: Unsupported salt type
@item
KRB5_KDB_BAD_ENCTYPE: Unsupported encryption type
@end enumerate
@node Kerberos V5 Magic Numbers Error Codes, ASN.1 Error Codes, Kerberos V5 Database Library Error Codes, Errors
@appendixsubsec Kerberos V5 Magic Numbers Error Codes
This is the Kerberos v5 magic numbers error code table.
@c error table numbering starts at 0
@enumerate 0
@item
KV5M_NONE: Kerberos V5 magic number table
@item
KV5M_PRINCIPAL: Bad magic number for krb5_principal structure
@item
KV5M_DATA: Bad magic number for krb5_data structure
@item
KV5M_KEYBLOCK: Bad magic number for krb5_keyblock structure
@item
KV5M_CHECKSUM: Bad magic number for krb5_checksum structure
@item
KV5M_ENCRYPT_BLOCK: Bad magic number for krb5_encrypt_block structure
@item
KV5M_ENC_DATA: Bad magic number for krb5_enc_data structure
@item
@iftex
KV5M_CRYPTOSYSTEM_ENTRY: Bad magic number for krb5_cryp@-to@-sys@-tem_entry
structure
@end iftex
@ifinfo
KV5M_CRYPTOSYSTEM_ENTRY: Bad magic number for krb5_cryptosystem_entry
structure
@end ifinfo
@item
KV5M_CS_TABLE_ENTRY: Bad magic number for krb5_cs_table_entry structure
@item
@iftex
KV5M_CHECKSUM_ENTRY: Bad magic number for krb5_check@-sum_en@-try structure
@end iftex
@ifinfo
KV5M_CHECKSUM_ENTRY: Bad magic number for krb5_checksum_entry structure
@end ifinfo
@item
KV5M_AUTHDATA: Bad magic number for krb5_authdata structure
@item
KV5M_TRANSITED: Bad magic number for krb5_transited structure
@item
KV5M_ENC_TKT_PART: Bad magic number for krb5_enc_tkt_part structure
@item
KV5M_TICKET: Bad magic number for krb5_ticket structure
@item
KV5M_AUTHENTICATOR: Bad magic number for krb5_authenticator structure
@item
KV5M_TKT_AUTHENT: Bad magic number for krb5_tkt_authent structure
@item
KV5M_CREDS: Bad magic number for krb5_creds structure
@item
KV5M_LAST_REQ_ENTRY: Bad magic number for krb5_last_req_entry structure
@item
KV5M_PA_DATA: Bad magic number for krb5_pa_data structure
@item
KV5M_KDC_REQ: Bad magic number for krb5_kdc_req structure
@item
KV5M_ENC_KDC_REP_PART: Bad magic number for @*
krb5_enc_kdc_rep_part structure
@item
KV5M_KDC_REP: Bad magic number for krb5_kdc_rep structure
@item
KV5M_ERROR: Bad magic number for krb5_error structure
@item
KV5M_AP_REQ: Bad magic number for krb5_ap_req structure
@item
KV5M_AP_REP: Bad magic number for krb5_ap_rep structure
@item
KV5M_AP_REP_ENC_PART: Bad magic number for @*
krb5_ap_rep_enc_part structure
@item
KV5M_RESPONSE: Bad magic number for krb5_response structure
@item
KV5M_SAFE: Bad magic number for krb5_safe structure
@item
KV5M_PRIV: Bad magic number for krb5_priv structure
@item
KV5M_PRIV_ENC_PART: Bad magic number for krb5_priv_enc_part structure
@item
KV5M_CRED: Bad magic number for krb5_cred structure
@item
KV5M_CRED_INFO: Bad magic number for krb5_cred_info structure
@item
KV5M_CRED_ENC_PART: Bad magic number for krb5_cred_enc_part structure
@item
KV5M_PWD_DATA: Bad magic number for krb5_pwd_data structure
@item
KV5M_ADDRESS: Bad magic number for krb5_address structure
@item
KV5M_KEYTAB_ENTRY: Bad magic number for krb5_keytab_entry structure
@item
KV5M_CONTEXT: Bad magic number for krb5_context structure
@item
KV5M_OS_CONTEXT: Bad magic number for krb5_os_context structure
@item
KV5M_ALT_METHOD: Bad magic number for krb5_alt_method structure
@item
KV5M_ETYPE_INFO_ENTRY: Bad magic number for @*
krb5_etype_info_entry structure
@item
KV5M_DB_CONTEXT: Bad magic number for krb5_db_context structure
@item
KV5M_AUTH_CONTEXT: Bad magic number for krb5_auth_context structure
@item
KV5M_KEYTAB: Bad magic number for krb5_keytab structure
@item
KV5M_RCACHE: Bad magic number for krb5_rcache structure
@item
KV5M_CCACHE: Bad magic number for krb5_ccache structure
@item
KV5M_PREAUTH_OPS: Bad magic number for krb5_preauth_ops
@item
KV5M_SAM_CHALLENGE: Bad magic number for krb5_sam_challenge
@item
KV5M_SAM_KEY: Bad magic number for krb5_sam_key
@item
KV5M_ENC_SAM_RESPONSE_ENC: Bad magic number for @*
krb5_enc_sam_response_enc
@item
KV5M_SAM_RESPONSE: Bad magic number for krb5_sam_response
@item
KV5M_PREDICTED_SAM_RESPONSE: Bad magic number for
krb5_predicted_sam_response
@item
KV5M_PASSWD_PHRASE_ELEMENT: Bad magic number for passwd_phrase_element
@end enumerate
@node ASN.1 Error Codes, GSSAPI Error Codes, Kerberos V5 Magic Numbers Error Codes, Errors
@appendixsubsec ASN.1 Error Codes
@c error table numbering starts at 0
@enumerate 0
@item
ASN1_BAD_TIMEFORMAT: ASN.1 failed call to system time library
@item
ASN1_MISSING_FIELD: ASN.1 structure is missing a required field
@item
ASN1_MISPLACED_FIELD: ASN.1 unexpected field number
@item
ASN1_TYPE_MISMATCH: ASN.1 type numbers are inconsistent
@item
ASN1_OVERFLOW: ASN.1 value too large
@item
ASN1_OVERRUN: ASN.1 encoding ended unexpectedly
@item
ASN1_BAD_ID: ASN.1 identifier doesn't match expected value
@item
ASN1_BAD_LENGTH: ASN.1 length doesn't match expected value
@item
ASN1_BAD_FORMAT: ASN.1 badly-formatted encoding
@item
ASN1_PARSE_ERROR: ASN.1 parse error
@end enumerate
@node GSSAPI Error Codes, , ASN.1 Error Codes, Errors
@appendixsubsec GSSAPI Error Codes
Generic GSSAPI Errors:
@c error table numbering starts at 0
@enumerate 0
@item
G_BAD_SERVICE_NAME: No @ in SERVICE-NAME name string
@item
G_BAD_STRING_UID: STRING-UID-NAME contains nondigits
@item
G_NOUSER: UID does not resolve to username
@item
G_VALIDATE_FAILED: Validation error
@item
G_BUFFER_ALLOC: Couldn't allocate gss_buffer_t data
@item
G_BAD_MSG_CTX: Message context invalid
@item
G_WRONG_SIZE: Buffer is the wrong size
@item
G_BAD_USAGE: Credential usage type is unknown
@item
G_UNKNOWN_QOP: Unknown quality of protection specified
@item
G_BAD_HOSTNAME: Hostname in SERVICE-NAME string could not be
canonicalized
@end enumerate
Kerberos 5 GSSAPI Errors:
@c error table numbering starts at 0
@enumerate 0
@item
KG_CCACHE_NOMATCH: Principal in credential cache does not match desired
name
@item
KG_KEYTAB_NOMATCH: No principal in keytab matches desired name
@item
KG_TGT_MISSING: Credential cache has no TGT
@item
KG_NO_SUBKEY: Authenticator has no subkey
@item
KG_CONTEXT_ESTABLISHED: Context is already fully established
@item
KG_BAD_SIGN_TYPE: Unknown signature type in token
@item
KG_BAD_LENGTH: Invalid field length in token
@item
KG_CTX_INCOMPLETE: Attempt to use incomplete security context
@item
KG_CONTEXT: Bad magic number for krb5_gss_ctx_id_t
@item
KG_CRED: Bad magic number for krb5_gss_cred_id_t
@item
KG_ENC_DESC: Bad magic number for krb5_gss_enc_desc
@end enumerate
@node kadmin Time Zones, , Errors, Appendix
@appendixsec kadmin Time Zones
This is a complete listing of the time zones recognized by the
@code{kadmin} command.
@table @b
@itemx gmt
Greenwich Mean Time
@itemx ut, utc
Universal Time (Coordinated).
@itemx wet
Western European Time. (Same as GMT.)
@itemx bst
British Summer Time. (1 hour ahead of GMT.)
@itemx wat
West Africa Time. (1 hour behind GMT.)
@itemx at
Azores Time. (2 hours behind GMT.)
@itemx bst
Brazil Standard Time. (3 hours behind GMT.) Note that the abbreviation
BST also stands for British Summer Time.
@itemx gst
Greenland Standard Time. (3 hours behind GMT.) Note that the
abbreviation GST also stands for Guam Standard Time.
@itemx nft
Newfoundland Time. (3.5 hours behind GMT.)
@itemx nst
Newfoundland Standard Time. (3.5 hours behind GMT.)
@itemx ndt
Newfoundland Daylight Time. (2.5 hours behind GMT.)
@itemx ast
Atlantic Standard Time. (4 hours behind GMT.)
@itemx adt
Atlantic Daylight Time. (3 hours behind GMT.)
@itemx est
Eastern Standard Time. (5 hours behind GMT.)
@itemx edt
Eastern Daylight Time. (4 hours behind GMT.)
@itemx cst
Central Standard Time. (6 hours behind GMT.)
@itemx cdt
Central Daylight Time. (5 hours behind GMT.)
@itemx mst
Mountain Standard Time. (7 hours behind GMT.)
@itemx mdt
Mountain Daylight Time. (6 hours behind GMT.)
@itemx pst
Pacific Standard Time. (8 hours behind GMT.)
@itemx pdt
Pacific Daylight Time. (7 hours behind GMT.)
@itemx yst
Yukon Standard Time. (9 hours behind GMT.)
@itemx ydt
Yukon Daylight Time. (8 hours behind GMT.)
@itemx hst
Hawaii Standard Time. (10 hours behind GMT.)
@itemx hdt
Hawaii Daylight Time. (9 hours behind GMT.)
@itemx cat
Central Alaska Time. (10 hours behind GMT.)
@itemx ahst
Alaska-Hawaii Standard Time. (10 hours behind GMT.)
@itemx nt
Nome Time. (11 hours behind GMT.)
@itemx idlw
International Date Line West Time. (12 hours behind GMT.)
@itemx cet
Central European Time. (1 hour ahead of GMT.)
@itemx met
Middle European Time. (1 hour ahead of GMT.)
@itemx mewt
Middle European Winter Time. (1 hour ahead of GMT.)
@itemx mest
Middle European Summer Time. (2 hours ahead of GMT.)
@itemx swt
Swedish Winter Time. (1 hour ahead of GMT.)
@itemx sst
Swedish Summer Time. (1 hours ahead of GMT.)
@itemx fwt
French Winter Time. (1 hour ahead of GMT.)
@itemx fst
French Summer Time. (2 hours ahead of GMT.)
@itemx eet
Eastern Europe Time; Russia Zone 1. (2 hours ahead of GMT.)
@itemx bt
Baghdad Time; Russia Zone 2. (3 hours ahead of GMT.)
@itemx it
Iran Time. (3.5 hours ahead of GMT.)
@itemx zp4
Russia Zone 3. (4 hours ahead of GMT.)
@itemx zp5
Russia Zone 4. (5 hours ahead of GMT.)
@itemx ist
Indian Standard Time. (5.5 hours ahead of GMT.)
@itemx zp6
Russia Zone 5. (6 hours ahead of GMT.)
@itemx nst
North Sumatra Time. (6.5 hours ahead of GMT.) Note that the
abbreviation NST is also used for Newfoundland Stanard Time.
@itemx sst
South Sumatra Time; Russia Zone 6. (7 hours ahead of GMT.) Note that
SST is also Swedish Summer Time.
@itemx wast
West Australian Standard Time. (7 hours ahead of GMT.)
@itemx wadt
West Australian Daylight Time. (8 hours ahead of GMT.)
@itemx jt
Java Time. (7.5 hours ahead of GMT.)
@itemx cct
China Coast Time; Russia Zone 7. (8 hours ahead of GMT.)
@itemx jst
Japan Standard time; Russia Zone 8. (9 hours ahead of GMT.)
@itemx kst
Korean Standard Time. (9 hours ahead of GMT.)
@itemx cast
Central Australian Standard Time. (9.5 hours ahead of GMT.)
@itemx cadt
Central Australian Daylight Time. (10.5 hours ahead of GMT.)
@itemx east
Eastern Australian Standard Time. (10 hours ahead of GMT.)
@itemx eadt
Eastern Australian Daylight Time. (11 hours ahead of GMT.)
@itemx gst
Guam Standard Time; Russia Zone 9. (10 hours ahead of GMT.)
@itemx kdt
Korean Daylight Time. (10 hours ahead of GMT.)
@itemx nzt
New Zealand Time. (12 hours ahead of GMT.)
@itemx nzst
New Zealand Standard Time. (12 hours ahead of GMT.)
@itemx nzdt
New Zealand Daylight Time. (13 hours ahead of GMT.)
@itemx idle
International Date Line East. (12 hours ahead of GMT.)
@end table
@contents
@bye
|