Vasily Khoruzhick wrote: > If I understood dbus philosophy correctly, server should be launched for each > user, it seems that client can connect to server only with same uid: when I > launch fprintd from account-1, and then launch verity from account-2, verify > says that it can't create proxy, and I found no ways to determine client uid > from server.
When running per-UID, one user will not be able to connect to another users server because they are running on different session busses. They are physically separate sessions. So in that case you do need one daemon per user. The problem there is that when one user's daemon has claimed and opened a fingerprint reader, it is not obvious why the 2nd user's daemon cannot access the device. This is the kind of problem I wanted to solve with fprintd. I would like fprintd to be able to reliably say "another user is using this device" and perhaps even say which user (if configured that way through PolicyKit or something). Having it as a systemwide daemon would allow this because there is one daemon shared between all users (on the global system bus) and that daemon has a unique world-view of the whole system (all users, programs, and fingerprint readers). To determine the client uid, use ConsoleKit. Daniel _______________________________________________ fprint mailing list [email protected] http://lists.reactivated.net/mailman/listinfo/fprint
