|
|
|
@ -47,3 +47,17 @@ The benefit is that such system would have a negligible impact on the CPU as |
|
|
|
|
the complexity of the routing determines the work that the server would do, |
|
|
|
|
as a normal user would just use the server to switch sound cards on the fly |
|
|
|
|
the performance impact is near zero. |
|
|
|
|
|
|
|
|
|
## An alternative to fprintd |
|
|
|
|
Libfprint is good enough, it currently is the only open source way to access |
|
|
|
|
fingerprint sensors, but the only two programs that I know use it are |
|
|
|
|
fprintd (from the same devs) and fingerprint-gui, both are not good. |
|
|
|
|
Fprintd could have been great as it is simple and implements a PAM module, but |
|
|
|
|
it requires polkit for some unknown reason, as for fingerprint-gui try to get |
|
|
|
|
it working. |
|
|
|
|
|
|
|
|
|
How should the alternative work? Kinda like fprintd but with just 2 components: |
|
|
|
|
- A fingerprint database manager to add, remove, modify and verify fingerprints |
|
|
|
|
- A PAM module for authentication |
|
|
|
|
Everything else can be done with a combination of those two components and shome |
|
|
|
|
shell glue, you don't really need anything else. |
|
|
|
|