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 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.
_______________________________________________ opensolaris-discuss mailing list [email protected]
