HOWTO: Fingerprint reading in Ubuntu with fprint

[bjo101]

Is there a way to configure fprint so that it asks me for my password if I can't provide a fingerprint. I tend to login to my laptop remotely when I'm not home and their is no fingerprint device on the remove computer,. Please tell me what lines to add to common auth and where to add them.

Thanks in advance.

Using Ubuntu 9.10 Karmic beta.

[yknivag]

Is there a way to configure fprint so that it asks me for my password if I can't provide a fingerprint. I tend to login to my laptop remotely when I'm not home and their is no fingerprint device on the remove computer,. Please tell me what lines to add to common auth and where to add them.

The answer is in the first post of this thread at point 4.

[bjo101]

Thank you for the response, however the post you refer to only defaults to the password if the attempt fails with the fingerprint like entering the wrong fingerprint. Is there a way to send a signal though the keyboard to bypass the fingerprint attempt and ask for the password, Possibly a timeout for finger scan. As I said I want to be able to get full access from remote machines with VNC that don't have a fingerprint reader on them.

Thanks in advance.

[yknivag]

If you set

auth required pam_fprint.so

then you can only log on with a fingerprint. If you use

auth sufficient pam_fprint.so

then the system will allow you to use a password instead.

[bjo101]

Plese disregard my last post I have since configured thinkfinger, which gace me the desired features.

Thanks for the help.

[ioio82]

Hello@all

this is what happened to me:

I set up fingerprint with a digitalpersona device.
Everything went fine, till I had difficulties at my finger getting recognized.

I edited /etc/pam.d/common-auth and commented out all references to auth sufficient pam_fprint.so.

Now my system won't let me login anymore with the password.

Not with the new login manager, neither through the terminal.

Does anybody have a solution? I did not change my user password.

Thank you.

[xyepblra]

Good day to everyone!
I followed the installation instructions and this process went nice and smooth untill

xyepblra@hp:~$ pam_fprint_enroll
This program will enroll your finger, unconditionally overwriting any selected print that was enrolled previously. If you want to continue, press enter, otherwise hit Ctrl+C

No devices detected.

But device IS THERE, because:

xyepblra@hp:~$ lsusb
Bus 003 Device 002: ID 138a:0001 DigitalPersona, Inc Fingeprint Reader

Any suggestions?

[xyepblra]

But device IS THERE, because:

xyepblra@hp:~$ lsusb
Bus 003 Device 002: ID 138a:0001 DigitalPersona, Inc Fingeprint Reader

Any suggestions?

Device is not supported...

[Nakebod]

Maybe a stupid question, but I haven't found the answer in this tread:
Is it possible to change the finger in the login screen?
So far it is always asking me for my left middle finger, and I'd prefer to (always) use my right index finger for authentication.

[nikhilbhardwaj]

great howto

works with karmic x64 too

but now it asks me for the fingerprint scan
and then the password

i'd like it to not ask for the password if the fingerprint scan is successful

here's my pam.d/common-auth

#
# /etc/pam.d/common-auth - authentication settings common to all services
#
# This file is included from other service-specific PAM config files,
# and should contain a list of the authentication modules that define
# the central authentication scheme for use on the system
# (e.g., /etc/shadow, LDAP, Kerberos, etc.).  The default is to use the
# traditional Unix authentication mechanisms.
#
# As of pam 1.0.1-6, this file is managed by pam-auth-update by default.
# To take advantage of this, it is recommended that you configure any
# local modules either before or after the default block, and use
# pam-auth-update to manage selection of other modules.  See
# pam-auth-update(8) for details.

# here are the per-package modules (the "Primary" block)
auth    sufficient                      pam_fprint.so 
auth    [success=1 default=ignore]      pam_unix.so nullok_secure
# here's the fallback if no module succeeds
auth    requisite                       pam_deny.so
# prime the stack with a positive return value if there isn't one already;
# this avoids us returning an error just because nothing sets a success code
# since the modules above will each just jump around