On Mon, 2007-08-20 at 20:18, Darren J Moffat wrote: > 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. > > That problem isn't unique to fingerprint readers, smartcards suffer from > exactly the same problem. In fact any USB device does - especially when > used with Sun Ray.
SunRay is not supposed to have this issue. Because the libusb on SunRay system creates different usb buses for each clients. A client can only see the devices plugged in itself. The usb devices in the different clients are isolated. Thus the keyboard/mouse/smartcard are bound with display in the client. I think the requirement of exporting X Biometric Devices is just for the systems that might have multiple remote X connections(for local X, they can share one). In fact, SunRay can resolve this issue. > > -- > Darren J Moffat -- Best Regards, GaoPeng Chen Call: +86-10-62673005 Ext: x82005 Sun Microsystem Inc. China
