Samba4 port: libkdc Interface - Revision history

Don: /* libkdc Entry Points */

2009-09-11T18:02:54Z

‎libkdc Entry Points

2009-09-11T14:29:02Z

‎krb5_kdc_windc_init()

2009-09-11T14:28:16Z

‎krb5_kdc_update_time()

2009-09-11T14:25:37Z

2009-09-11T14:23:14Z

‎krb5_kdc_process_request()

2009-09-11T14:16:28Z

‎krb5_kdc_process_request()

2009-09-11T14:15:55Z

‎krb5_kdc_process_krb5_request()

2009-09-11T01:44:25Z

‎krb5_kdc_process_krb5_request()

2009-09-10T20:51:29Z

‎krb5_kdc_process_krb5_request()

2009-09-10T20:45:08Z

‎krb5_kdc_get_config()

@@ Line 70: / Line 70: @@
 |}
-The following subsections describe only the four libkdc entry-points
+The following subsections describe primarily the four libkdc entry-points that Samba4 uses.
 ----

@@ Line 152: / Line 152: @@
 handles AD-style account-authorization controls,
 and MIT-krb doesn't yet have a windc plugin.
 The krb5_kdc_windc_init() entry point calls several Heimdal
 functions that MIT-krb lacks:

@@ Line 142: / Line 142: @@
 # kdc_process() calls krb5_kdc_update_time() at ticket-request time, just before kdc_process() calls krb5_kdc_process_krb5_request();
 So, this entry point requires no porting effort.
 ----

@@ Line 121: / Line 121: @@
 # krb5_kdc_process_krb5_request() gets used by Samba4
 # krb5_kdc_process_request() doesn't (see below).
 === krb5_kdc_process_request() ===
@@ Line 236: / Line 278: @@
 # krb5_kdc_process_krb5_request() gets used by Samba4
 # krb5_kdc_process_request() doesn't.
 ----

@@ Line 123: / Line 123: @@
 === krb5_kdc_process_request() ===
 The Heimdal KDC catches client-requests by calling
 the libkdc entry-point krb5_kdc_process_request(),

@@ Line 128: / Line 128: @@
 {| class="wikitable sortable" width="100%" border="1" style="border-collapse: collapse; border: 1px solid #dfdfdf;"
-| bgcolor="#666666" |<font color="#ffffff">'''Protocol'''</font>
+| bgcolor="#CCCCCC" |<font color="#ffffff">'''Protocol'''</font>
-| bgcolor="#666666" |<font color="#ffffff">'''Heimdal fcn''' </font>
+| bgcolor="#CCCCCC" |<font color="#ffffff">'''Heimdal fcn''' </font>
-| bgcolor="#666666" |<font color="#ffffff">'''MIT-krb fcn'''</font>
+| bgcolor="#CCCCCC" |<font color="#ffffff">'''MIT-krb fcn'''</font>
 |-

@@ Line 76: / Line 76: @@
 === krb5_kdc_process_krb5_request() ===
-FIX: wrong fcn:  Samba4 passes client-requests to the KDC by calling
+Samba4 passes client-requests to the KDC by calling
 the libkdc entry-point krb5_kdc_process_krb5_request(),
 which invokes the following Heimdal KDC functions:
@@ Line 84: / Line 84: @@
 | bgcolor="#ff6600" |<font color="#ffffff">'''Heimdal fcn''' </font>
 | bgcolor="#ff6600" |<font color="#ffffff">'''MIT-krb fcn'''</font>
 |-

@@ Line 181: / Line 181: @@
 # MIT-krb no longer supports v4 operation, as of MIT v1.7;
 # Samba4 doesn't actually use the Windows "digest auth" protocols;
-# UMichigan's hx509 protocol may not be necessary for Samba4;
+# U.Michigan's hx509 protocol may not be necessary for Samba4;
 # Carnegie-Mellon's AFS project seems to have deprecated kaserver.

@@ Line 192: / Line 192: @@
 Heimdal has a run-time apparatus for managing the
 KDC's configuration, while MIT-krb uses a simple configuration file.
 # Samba4 reads the KDC's config-settings from a config-file, and then passes the settings to the KDC, using the krb5_kdc_configuration{} structure.
 # Samba4 uses the libkdc entry-point '''krb5_kdc_get_config()''' to initialize the krb5_kdc_configuration{} structure;