Yes, it seems to be good to bind the biometric device with keyboard/display in X level. But it just works for the biometric devices that captures images. The PAM module receives the image from application and verify it. If the verification function is integrated in the device firmware, the PAM module doesn't know how to handle it for it can't access the device. Further, much additional work should be done to support biometric device in X level. IMO, it's not so valuable. Biometric device is not in the importance level as keyboard for X. Thanks.
On Sat, 2007-08-18 at 01:10, James Carlson wrote: > Brian Cameron writes: > > Using this approach, when a user puts their finger on the fingerprint > > reader, > > a daemon could tell GDM to restart using the fingerprint PAM stack. This > > sort of approach could also work and wouldn't require extending PAM at > > all. > > One of the key questions underlying all of this has been the question > of *which* GDM, if there are multiple, should get the event from > *which* reader. If you bind together the biometric reader with the > existing keyboard/mouse/ display group, then it's easy to see how this > works. If the fingerprint reader is dangling in space, it's less > obvious how it works. > > -- > James Carlson, Solaris Networking <james.d.carlson at sun.com> > Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 > MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 -- Best Regards, GaoPeng Chen Call: +86-10-62673005 Ext: x82005 Sun Microsystem Inc. China
