[16026] in Kerberos_V5_Development
Re: Plugin project proposal
daemon@ATHENA.MIT.EDU (Jeffrey Hutzelman)
Sun Aug 1 21:15:13 2010
Date: Sun, 01 Aug 2010 21:15:03 -0400
From: Jeffrey Hutzelman <jhutz@cmu.edu>
To: Nicolas Williams <Nicolas.Williams@oracle.com>,
Zhanna Tsitkova <tsitkova@mit.edu>
Message-ID: <95B7C95A38EE70F357FD0CA6@atlantis.pc.cs.cmu.edu>
In-Reply-To: <20100715193126.GJ22556@oracle.com>
MIME-Version: 1.0
Content-Disposition: inline
Cc: rra@stanford.edu, krbdev@mit.edu, jhutz@cmu.edu
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu
--On Thursday, July 15, 2010 02:31:28 PM -0500 Nicolas Williams
<Nicolas.Williams@oracle.com> wrote:
> On Thu, Jul 15, 2010 at 03:06:11PM -0400, Zhanna Tsitkova wrote:
>> On Jul 15, 2010, at 2:57 PM, Nicolas Williams wrote:
>> > What is used as a key to the table?
>>
>> Suppose we have the following v-table for plugin password quality:
>> /* PWD_QLTY API */
>> typedef struct {
>> int version;
>> char plugin_id[MAX_PL_NAME_LEN];
>> kadm5_ret_t (*pwd_qlty_init)(kadm5_server_handle_t);
>> void (*pwd_qlty_cleanup)();
>> kadm5_ret_t (*pwd_qlty_check)(kadm5_server_handle_t, char*,int,
>> kadm5_policy_ent_t, krb5_principal);
>> } plugin_pwd_qlty;
>>
>> Then the key may be "pwd_qlty_check"
>
> I think this is still ridiculously complicated.
>
> It'd all be simpler with a dlsym() over v-table approach
Yes. Yes it would. After all, what's being described here is a
reimplementation of symbol table lookup, again with no advantage I can see
over use of dlsym(). But, I seem to recall we've had that argument already.
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
