On Sun, 2008-08-03 at 17:58 -0700, Brian Aker wrote: > Hi! > > I worked out an example PAM authentication plugin this weekend. This > is about what I learned: > > Server: > > There is quite a bit more that needs to be done on the server right now: > 1) Final cleanup of old security context. > 2) THD needs to be split out sooner then later. > 3) We need to private'ize more of THD. > 4) We use a VOID pointer to pass in a structure to plugins for init/ > finalize. I keep finding myself wondering if that should be a base > class that we inherit from (aka I am starting to see certain patterns > reoccurring in plugins).
I'm increasingly of the view that teh plugin init function should then
call functions in the server to register functionality.
not the existing behaviour of casting then filling out the struct passed
in as void*.
e.g.
struct auth_basic foo = { blah, blah blah };
plugin_foo_init()
{
register_auth_module(&foo);
register_func_module(&f);
}
--
Stewart Smith ([EMAIL PROTECTED])
http://www.flamingspork.com/
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
