Difference between revisions of "Talk:Integrated Fingerprint Reader"

From ThinkWiki
Jump to: navigation, search
 
(5 intermediate revisions by 5 users not shown)
Line 9: Line 9:
 
-- Josiah
 
-- Josiah
  
== Fingerprint reader hiccups ==
+
== Binary UPEK driver - Why that complicated??? ==
  
any body else notice that the fingerprint reader doesn't work very well or doesn't work at all if you have been using the notebook for sometime?
+
I don't want to mess anything, but it seems to me that the information about the binary UPEK driver is completely outdated and wrong. According to this page and to the [http://www.thinkwiki.org/wiki/How_to_enable_the_fingerprint_reader HOWTO], the UPEK driver must be compiled, needs a lot of hacks and tweaks and isn't really stable. Well, that's not true at all!
 +
In fact, UPEK provides a nice deb-Package here [http://www.upek.com/support/downloads/linux/] which installs immediately. After that you need to go to System -> Administration -> Fingerprint Enrollment and register you fingerprint(s). Reboot your machine and it works. The only inconvenience is that you must hit Enter after scanning your finger but in my view that's not that bad. I run Ubuntu Lucid and thinkfinger doesn't work for me at all (although it was fine in Jaunty+Karmic), whereas fprint has some really nasty bugs [https://bugs.launchpad.net/ubuntu/+source/pam-fprint/+bug/347778]. Both thinkfinger and fprint aren't being developed actively anymore (thinkfinger -> Last update:  2007-03-30 , fprint -> Last update: 23.11.2008). UPEK driver, however, works fine. So, why not UPEK?
  
I'm thinking because of the heat generated from the hdd
 
  
== HowTo :) ==
 
  
Disclaimer: This is how I got the fingerprint reader on my T43 to work. It can _NOT_ yet be used to log me into the system. Working on that,
+
== Fingerprint reader hiccups ==
  
This is on ubuntu breezy.
+
any body else notice that the fingerprint reader doesn't work very well or doesn't work at all if you have been using the notebook for sometime?
  
get all required devel libs and tools (gcc, g++, pam-dev, etc.)
+
I'm thinking because of the heat generated from the hdd
I could not compile bioapi with the graphical Qt tools
 
* wget http://www.qrivy.net/~michael/blua/bioapi/bioapi-1.2.2.tar.bz2
 
* tar xjf bioapi-1.2.2.tar.bz2
 
* cd bioapi-1.2.2
 
* ./configure --with-Qt-dr=no
 
* make
 
then as root
 
* make install
 
beware that checkinstall will not work!
 
go to http://www.qrivy.net/~michael/blua/upek-bsp.html and download TFMESS_BSP_LIN_1.0beta2.zip
 
unzip it into a seperate folder, as it will not create one
 
as root
 
* sh install.sh
 
* chmod 777 -R /usr/local/var/bioapi/
 
actually this depends on where you installed, if you did as i wrote, it should work otherwise you probably know what you're doing anyways :)
 
* touch /var/log/BSP.log && chmod 666 /var/log/BSP.log
 
* chmod 666 /proc/bus/usb/`lsusb | grep "0483:2016" | sed -e "s/Bus\ \(.*\)\ Device\ \(.*\):\ .*/\1\/\2/"`
 
now go to the folder where you extracted TFMESS_BSP_LIN_1.0beta2.zip
 
* cd NonGUI_Sample
 
* ./Sample
 
Now i hope it works, otherwise mail me: t43fingerprint@badcode.de
 
 
 
Another thing i got to work: gdm login with pam_bioapi *freu*
 
 
 
what i did:
 
 
 
* wget http://www.qrivy.net/~michael/blua/pam_bioapi/pam_bioapi-0.2.1.tar.bz2
 
* tar xjf pam_bioapi-0.2.1.tar.bz2
 
* ./configure && make
 
as root
 
* make install
 
 
 
now use the sample tool from the fingerprint reader to create <username>.bir
 
<username> _must_ be the username you want to login with, gdm broke for me for any login name that had no .bir file
 
 
 
try:
 
* BioAPITest | grep -A2 Fingerprint | tail -n1 | cut -b 12-
 
it should print something like "{5550454b2054464d2f45535320425350}"
 
if it does:
 
* mkdir /etc/bioapi1.10/pam`BioAPITest | grep -A2 Fingerprint | tail -n1 | cut -b 12-`
 
* cp <username>.bir /etc/bioapi1.10/pam`BioAPITest | grep -A2 Fingerprint | tail -n1 | cut -b 12-`
 
  
now comes a distribution specific part. on ubuntu i can modify /etc/pam.d/common-auth to look like this:
+
== 5-way navigation ==
  
#
+
The ''5-way navigation'' mentioned in the [http://www.upek.com/support/pdf/UPEK_flyer_TCS3_TCD4.pdf spec sheet] sounds interesting.
# /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.
 
#
 
auth    sufficient      pam_bioapi.so {5550454b-2054-464d-2f45-535320425350} /etc/bioapi1.10/pam
 
auth    required        pam_unix.so nullok_secure
 
  
and pam immediatelly starts to use the fingerprint reader to do local authorization (e.g. sudo/gdm use the fingerprint reader)
+
== Hot Much? ==
I found this out by try and success, if this is plain wrong, wikorrect me :)
+
Speaking of heat, the fingerprint reader on my T60 running FC6 gets very warm at times. Do others experience this? --[[User:Whizkid|Whizkid]] 18:23, 6 June 2007 (UTC)
Now my gdm pops up a (ugly) image to swipe my finger and... magic I can login without a password
+
: Same here on my T60. (I have not even enabled fingerprint reader yet.) -- [[User:Eismcsquare|Eismcsquare]] 21:32, 5 June 2008 (CEST)
  
I'd be glad to help out if you have questions.
+
== Pre-Boot-Authentication ==
  
Sumedha
+
How do I set up Pre-Boot-Authentication (PBA) with the Fingerprint reader?
 +
Is this even possible?

Latest revision as of 18:52, 3 May 2010

I was just wondering what was happening with this, it would be really great for this to work.

Slashdot posted about linuxbiometrics.com, and I found this forum post there.

--64.180.113.159 23:27, 10 Apr 2005 (CEST)

There is a possibility that a beta program will be occuring around August or Sept. this year '05. Keep your eyes (or news aggregator) on linuxbiometrics.com for the latest announcements.

-- Josiah

Binary UPEK driver - Why that complicated???

I don't want to mess anything, but it seems to me that the information about the binary UPEK driver is completely outdated and wrong. According to this page and to the HOWTO, the UPEK driver must be compiled, needs a lot of hacks and tweaks and isn't really stable. Well, that's not true at all! In fact, UPEK provides a nice deb-Package here [1] which installs immediately. After that you need to go to System -> Administration -> Fingerprint Enrollment and register you fingerprint(s). Reboot your machine and it works. The only inconvenience is that you must hit Enter after scanning your finger but in my view that's not that bad. I run Ubuntu Lucid and thinkfinger doesn't work for me at all (although it was fine in Jaunty+Karmic), whereas fprint has some really nasty bugs [2]. Both thinkfinger and fprint aren't being developed actively anymore (thinkfinger -> Last update: 2007-03-30 , fprint -> Last update: 23.11.2008). UPEK driver, however, works fine. So, why not UPEK?


Fingerprint reader hiccups

any body else notice that the fingerprint reader doesn't work very well or doesn't work at all if you have been using the notebook for sometime?

I'm thinking because of the heat generated from the hdd

5-way navigation

The 5-way navigation mentioned in the spec sheet sounds interesting.

Hot Much?

Speaking of heat, the fingerprint reader on my T60 running FC6 gets very warm at times. Do others experience this? --Whizkid 18:23, 6 June 2007 (UTC)

Same here on my T60. (I have not even enabled fingerprint reader yet.) -- Eismcsquare 21:32, 5 June 2008 (CEST)

Pre-Boot-Authentication

How do I set up Pre-Boot-Authentication (PBA) with the Fingerprint reader? Is this even possible?