danvics/python-validity
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

corrected docs for fedora

Browse source
This commit is contained in:
fumnanya 2024-08-07 11:34:01 +01:00 committed by GitHub
parent ca21528b27
commit c8afc3b2cd
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 33 additions and 19 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

20
README.md
View file

@ -44,7 +44,7 @@ $ fprintd-enroll
On Fedora Linux On Fedora Linux
``` ```
$ sudo dnf copr enable tigro/python-validity $ sudo dnf copr enable sneexy/python-validity
$ sudo dnf install open-fprintd fprintd-clients fprintd-clients-pam python3-validity $ sudo dnf install open-fprintd fprintd-clients fprintd-clients-pam python3-validity
...wait a bit... ...wait a bit...
$ fprintd-enroll $ fprintd-enroll
@ -54,7 +54,7 @@ $ fprintd-enroll
#### List devices failed #### List devices failed
If `fprintd-enroll` returns with `list_devices failed:`, you can check If `fprintd-enroll` returns with `list_devices failed:` or `GDBus.Error:net.reactivated.Fprint.error.NoSuchDevice`, you can check
the logs of the `python3-validity` daemon using `$ sudo systemctl status python3-validity`. the logs of the `python3-validity` daemon using `$ sudo systemctl status python3-validity`.
If it's not running, you can enable and/or start it by substituting `status` with `enable` or `start`. If it's not running, you can enable and/or start it by substituting `status` with `enable` or `start`.
@ -86,7 +86,17 @@ $ sudo systemctl enable open-fprintd-resume open-fprintd-suspend
For even more error procedures, check [this Arch comment thread](https://aur.archlinux.org/packages/python-validity/#comment-755904) or [this python-validity bug comment thread](https://github.com/uunicorn/python-validity/issues/3). For even more error procedures, check [this Arch comment thread](https://aur.archlinux.org/packages/python-validity/#comment-755904) or [this python-validity bug comment thread](https://github.com/uunicorn/python-validity/issues/3).
## Enabling fingerprint for system authentication ## Enabling fingerprint for system authentication
To enable fingerprint login, if it doesn't come automatically, run
if it doesn't come automatically, you might need to make changes to files in `/etc/pam.d` to enable fingerprint login (depending on your distro).
- On Fedora, use `authselect`[^1]:
```
$ sudo authselect current
$ sudo authselect enable-feature with-fingerprint
$ sudo authselect apply-changes
```
- On other distros, run
``` ```
$ sudo pam-auth-update $ sudo pam-auth-update
``` ```
@ -96,6 +106,8 @@ will be tried first, and only if that fails or times out will you see
a password prompt. Take note of the led-stripe above the fingerprint a password prompt. Take note of the led-stripe above the fingerprint
sensor to see whether it is active. sensor to see whether it is active.
You can also take a look at [Configuration: fprint](https://wiki.archlinux.org/title/Fprint#Configuration) on the Arch Wiki for an idea how the file should be modified.
### The actual change from pam-auth-update ### The actual change from pam-auth-update
The above mentioned command `$ sudo pam-auth-update` simply makes a small modification to /etc/pam.d/common-auth: The above mentioned command `$ sudo pam-auth-update` simply makes a small modification to /etc/pam.d/common-auth:
@ -227,3 +239,5 @@ If you are curious you can enable tracing to see what flows in and out of device
10: User S-1-5-21-394619333-3876782012-1672975908-3333 with 0 fingers: 10: User S-1-5-21-394619333-3876782012-1672975908-3333 with 0 fingers:
>>> >>>
``` ```
[^1]: Credit to u/trollpunny: [https://old.reddit.com/r/Fedora/comments/oik8sq/comment/h4xvrqv/?utm_source=share&utm_medium=web2x&context=3](https://old.reddit.com/r/Fedora/comments/oik8sq/comment/h4xvrqv/?utm_source=share&utm_medium=web2x&context=3)