Talk:Integrated Fingerprint Reader - Revision history

Bombenbach at 17:52, 3 May 2010

2010-05-03T17:52:33Z

Eismcsquare: /* Hot Much? */

2008-06-05T19:32:41Z

‎Hot Much?

Idmep: New section: Pre-Boot-Authentication

2008-03-02T16:01:46Z

New section: Pre-Boot-Authentication

Whizkid: Hot reader, anyone?

2007-06-06T18:23:15Z

Hot reader, anyone?

H8s: 5-way navigation

2006-09-23T17:19:04Z

5-way navigation

137.226.12.107 at 13:55, 24 October 2005

2005-10-24T13:55:15Z

137.226.12.107 at 13:49, 24 October 2005

2005-10-24T13:49:28Z

137.226.12.107 at 10:45, 24 October 2005

2005-10-24T10:45:22Z

137.226.147.140 at 07:20, 24 October 2005

2005-10-24T07:20:02Z

210.1.84.250: Fingerprint reader hiccups

2005-08-16T09:52:54Z

Fingerprint reader hiccups

← Older revision		Revision as of 17:52, 3 May 2010
Line 8:		Line 8:

	-- Josiah		-- 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 [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?
		+
		+

	== Fingerprint reader hiccups ==		== Fingerprint reader hiccups ==

@@ Line 21: / Line 21: @@
 == Hot Much? ==
 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)
 == Pre-Boot-Authentication ==

← Older revision		Revision as of 16:01, 2 March 2008
Line 21:		Line 21:
	== Hot Much? ==		== Hot Much? ==
	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)		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)
		+
		+	== Pre-Boot-Authentication ==
		+
		+	How do I set up Pre-Boot-Authentication (PBA) with the Fingerprint reader?
		+	Is this even possible?

← Older revision		Revision as of 18:23, 6 June 2007
Line 18:		Line 18:

	The ''5-way navigation'' mentioned in the [http://www.upek.com/support/pdf/UPEK_flyer_TCS3_TCD4.pdf spec sheet] sounds interesting.		The ''5-way navigation'' mentioned in the [http://www.upek.com/support/pdf/UPEK_flyer_TCS3_TCD4.pdf 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? --[[User:Whizkid\|Whizkid]] 18:23, 6 June 2007 (UTC)

← Older revision		Revision as of 17:19, 23 September 2006
Line 14:		Line 14:

	I'm thinking because of the heat generated from the hdd		I'm thinking because of the heat generated from the hdd
		+
		+	== 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.

← Older revision		Revision as of 13:55, 24 October 2005
Line 14:		Line 14:

	I'm thinking because of the heat generated from the hdd		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,~~
−
−	~~This is on ubuntu breezy.~~
−
−	~~get all required devel libs and tools (gcc, g++, pam-dev, etc.)~~
−	~~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:~~
−
−	#
−	~~# /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)~~
−	~~I found this out by try and success, if this is plain wrong, wikorrect me :)~~
−	~~Now my gdm pops up a (ugly) image to swipe my finger and... magic I can login without a password~~
−
−	~~I'd be glad to help out if you have questions.~~
−
−	~~Sumedha~~

← Older revision		Revision as of 13:49, 24 October 2005
Line 55:		Line 55:

	now use the sample tool from the fingerprint reader to create <username>.bir		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

−	...~~coffee break~~... ~~brb~~	+	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:
		+
		+	#
		+	# /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)
		+	I found this out by try and success, if this is plain wrong, wikorrect me :)
		+	Now my gdm pops up a (ugly) image to swipe my finger and... magic I can login without a password
		+
		+	I'd be glad to help out if you have questions.
		+
		+	Sumedha

@@ Line 18: / Line 18: @@
 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,
 get all required devel libs and tools (gcc, g++, pam-dev, etc.)
@@ Line 41: / Line 43: @@
 * ./Sample
 Now i hope it works, otherwise mail me: t43fingerprint@badcode.de

← Older revision		Revision as of 07:20, 24 October 2005
Line 14:		Line 14:

	I'm thinking because of the heat generated from the hdd		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,
		+
		+	get all required devel libs and tools (gcc, g++, pam-dev, etc.)
		+	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

← Older revision		Revision as of 09:52, 16 August 2005
Line 8:		Line 8:

	-- Josiah		-- Josiah
		+
		+	== 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