On Thu, 2007-06-14 at 17:52, Giles Turner wrote: > On 6/14/07, Gaopeng Chen - Sun China <[EMAIL PROTECTED]> wrote: > > > > On Thu, 2007-06-14 at 17:24, Giles Turner wrote: > > > What if I wanted to use pam_bioapi instead of pam_fpr before bioapi is > > > imported? > > > > I have to say "no" before bioapi is imported. But it doesn't matter > > since the security services (such as login, xscreensaver, etc) work upon > > the PAM APIs. pam_fpr or pam_bioapi is just a pluggable module in the > > PAM stack. Thanks. > > "No" as in libfpr will not support bioapi until it is imported if libfpr can be considered as the fingerprint dirver, so it can be easily wrapped by bioapi. What I mean is you can't use pam_bioapi until bioapi is imported. But you can use pam_fpr, since it has the same function with pam_bioapi. Thanks.
> ever? It does matter. If libfpr does not support bioapi, then I cannot > use pam_bioapi with libfpr supported devices but I suppose I will be > told get a bioapi driver from vendor. > > > > > > After bioapi is imported in the future. the current diagram will be > > > > changed from, > > > > > > > > PAM > > > > | > > > > pam_fpr > > > > | > > > > libfpr > > > > > > > > to, > > > > > > > > PAM > > > > | > > > > pam_bio > > > > | > > > > bioapi > > > > | > > > > ---------------------------------- > > > > | | | | > > > > libfpr libiris libvoice ... > > > > > > > > > > > > So that libfpr still keeps the driver level, we don't need to do much > > > > overlapped work. Thanks. -- Best Regards, GaoPeng Chen Call: +86-10-62673005 Ext: x82005 Sun Microsystem Inc. China _______________________________________________ opensolaris-discuss mailing list [email protected]
