From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Raghav Gururajan <rvgn@disroot.org>
Cc: help-guix@gnu.org
Subject: Re: Fingerprint Service
Date: Thu, 16 May 2019 12:37:48 +0200 [thread overview]
Message-ID: <87v9yahegz.fsf@nckx> (raw)
In-Reply-To: <69c6523e63f2b4e3f02dcf9eb9c3e079@disroot.org>
[-- Attachment #1: Type: text/plain, Size: 1044 bytes --]
Raghav Gururajan wrote:
>>> After Danny's fix, fprintd just works on my X230T:
>>>
>>> λ fprintd-enroll
>>> Using device /net/reactivated/Fprint/Device/0
>>> Enrolling right-index-finger finger.
>>>
>>> …and the finger print reader lights right up!
>>
>> That's cool! I will try and get back to you. :-)
>
> Typing "λ fprintd-enroll" or "fprintd-enroll" in the terminal
> throws "command not found".
~ λ is my bash prompt :-)
fprintd-* commands are part of the ‘fprintd’ package. ‘guix
install fprintd’ and try again.
Now, to actually use the reader for ‘authentication’ to existing
services (screen lockers, display managers, prompts…) you'll
probably have to write your own PAM rule. I haven't tried that.
I've only played with the reader; I'm not sure I have any real use
for it.
Biometrics make terrible passwords. They're more like the
‘something you have’ of two-factor authentication, but much more
painful to steal — mainly for the owner.
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2019-05-16 10:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 14:11 Fingerprint Service Raghav Gururajan
2019-05-15 21:10 ` Ludovic Courtès
2019-05-15 21:22 ` Tobias Geerinckx-Rice
2019-05-16 4:48 ` Raghav Gururajan
2019-05-16 4:51 ` Raghav Gururajan
2019-05-16 8:06 ` Raghav Gururajan
2019-05-16 10:37 ` Tobias Geerinckx-Rice [this message]
2019-05-16 10:49 ` Raghav Gururajan
2019-05-17 15:22 ` Raghav Gururajan
2019-05-16 8:08 ` Raghav Gururajan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v9yahegz.fsf@nckx \
--to=me@tobias.gr \
--cc=help-guix@gnu.org \
--cc=rvgn@disroot.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).