Message-Id: <9512131214.AA00817@jimi.MIT.EDU>
To: epeisach@MIT.EDU
Cc: cvs-krb5@MIT.EDU
Subject: Re: keytab/db files 
In-Reply-To: Your message of "Tue, 12 Dec 1995 11:30:20 EST."
             <9512121630.AA16420@kangaroo.mit.edu> 
Date: Wed, 13 Dec 1995 07:14:47 EST
From: Christopher Provenzano  <proven@MIT.EDU>


> 
> Wouldn't it make sense to make the functions a subdir of kdb?
> After fixing the lib/krb5/Makefile.in to look at the keytab/db subdir
> and tring to build shared libraries, the krb5 library now depends on -lkdb5
> 
> The following are unresolved:
> 
> krb5_db_open_database
> krb5_db_get_principal
> krb5_dbm_db_get_mkey
> krb5_dbe_find_enctype
> krb5_dbekd_decrypt_key_data
> krb5_dbe_free_contents
> krb5_db_close_database
> 
> From what I can tell libkrb5 does not depend on any files in keytab/db/*
> (unless I am missing something here). It seems to me that libkdb is the
> proper place for this extension to the keytab system. 
> 
> In fact the keytab system already has the means with "krb5_kt_register"
> to add new keytype system to the environment - which is what you are
> doing. 

That won't work because the resolve routine krb5_ktkdb_resolve() needs a
pointer to a krb5_db_context which can't be passed through by 
krb5_kt_resolve().

> 
> If you really want to be silly, perhaps the proper place might even be
> libkrb5util... 
> 
> Opionions?

In order to do things right we would need to remove all libkrb5 dependencies 
from the libkdb library and replace the encrypt/decrypt routines with the raw
crypto routines, and then link with libkrb5 before libkdb. This isn't going
to happen though so I moved the kdb keytab routines to libkdb.

CAP