Pasword quality pluggable interface project review

Zhanna Tsitkova tsitkova at MIT.EDU
Mon Aug 30 12:49:49 EDT 2010

On Aug 30, 2010, at 11:54 AM, Greg Hudson wrote:

> On Mon, 2010-08-30 at 11:38 -0400, Marcus Watts wrote:
>> By "new plugin model" do you mean krb5int_open_plugin_dirs /
>> krb5int_get_plugin_dir_data or something else?  If you mean these
>> functions then it's already done.  If it's something else, then
>> I guess it depends on how closely the new functionality matches  
>> these.
> What we arrived at doesn't have the properties you discussed about the
> PAM framework:
> * Module registrations aren't parameterized (but modules can read
> associations from the profile, so they don't require separate config
> files).
> * Module registrations aren't ordered.
> * Registration of built-in modules is automatic, although built-in
> modules can be disabled.
> * Modules cannot be multiply registered; the end result of module
> registration is a mapping of name to (unique) module, even for
> one-to-many interfaces (such as password quality) where module names  
> are
> unimportant.
> While we still have the technical freedom to replace this model with
> something more PAM-like, I'm not currently convinced that it's
> desirable.

Well, the password quality is the first plugin module that we attempt  
to implement under 
,  i.e. the first test for the flexibility of the plugin architectural  

I believe that one must take closer look at the requirements as they  
are described by Marcus and some are mentioned above : ordered module  
registration, plugin interdependencies, multiple and parameterized  
registration of the modules. All of them where discussed before but in  
lack of the real use-cases were postponed.


More information about the krbdev mailing list