Remove errcode_2_string and release_errcode_string from the DAL table,

and stop using them in kdb5.c.  Modules can simply set error messages
in the krb5 context on error.

ticket: 6749
status: open

git-svn-id: svn://anonsvn.mit.edu/krb5/trunk@24159 dc483132-0cff-0310-8789-dd5450dbe970

1 files changed, 0 insertions, 15 deletions

diff --git a/src/include/kdb.h b/src/include/kdb.h
index dd1e613be6..e8e82eb5b8 100644
--- a/src/include/kdb.h
+++ b/src/include/kdb.h
@@ -1133,21 +1133,6 @@ typedef struct _kdb_vftabl {
     void (*db_free_policy)(krb5_context kcontext, osa_policy_ent_t val);
 
     /*
-     * Optional: Convert an error code returned by a module function (casted
-     * from krb5_error_code to long) into a string.  If this function is
-     * implemented, libkdb5 will invoke it and call krb5_set_error_message with
-     * the result.  This function may never return NULL.
-     *
-     * This function is not productively implemented in current modules, and it
-     * is better for a module to simply call krb5_set_error_message inside
-     * modules when appropriate.
-     */
-    const char *(*errcode_2_string)(krb5_context kcontext, long err_code);
-
-    /* Optional: Free an error string returned by errcode_2_string. */
-    void (*release_errcode_string)(krb5_context kcontext, const char *msg);
-
-    /*
      * Mandatory: Has the semantics of realloc(ptr, size).  Callers use this to
      * allocate memory for new or changed principal entries, so the module
      * should expect to potentially see this memory in db_free_principal.