Emile Nijssen | 25 Sep 22:26 2013
Picon

Multiple fingers

Hey all,

I'm writing a simple application for my front door, and would like to register many people.. however, the current API seems to only allow one person with 10 fingers.

Is there an easy way to just 'keep registering fingers' and upon verifying just check if there is a match in the database? I really do not care about which finger etc, just if this is a familiar finger :-)

Thanks in advance!

WeeJeWel
_______________________________________________
fprint mailing list
fprint <at> lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/fprint
Linos | 13 Sep 13:38 2013
Picon

DigitalPersona UareU 4500

Hi,
	i have finally bought one unit of this model to test it.

I am testing using fingerprint-gui right now, later i will need to
integrate with my own software.

It works but verification seems to work much better in windows with the
u.are.u SDK.

Fingerprint-gui read my finger only one time to enroll it, in windows i
have to do 4 corrects readings to enroll one finger.

My finger doesn't work very well with libfprint (fail to verify half of
the times), but works every time using u.are.u SDK.

From what i can read here
http://www.freedesktop.org/wiki/Software/fprint/libfprint/uru4000/ it
seems that the matching/verification process it's done by libfprint,
maybe this is the difference?

Regards,
Miguel Angel.
Vojtěch Polášek | 12 Sep 23:43 2013
Picon

New ubuntu user

Hi,
my name is Vojta and I am a blind Linux user from Czech Republic.
I have recently bought Lenovo Thinkpad X230 with Upek fingerprint reader
(sorry for possible misspell).
I would like to try it with fprint, but I have the following problem:
I want to use my fingerprint just for sudo.
So I added your PPA to my Ubuntu 12.04 installation, installed fprintd
with dependencies.
When using fprintd-enroll, everything works, but when doing sudo, it
prompts me for a password first and when I just press enter, it says,
that no fingerpint could be found in the hardware.
I tried enrolling with
pam_fprint_enroll but at the end it exits with data storage failure
error -1.
And still I am aksed for password first and after then for my fingerprint.
This is content of my /etc/pam.d/sudo:

#%PAM-1.0

#auth       required   pam_env.so readenv=1 user_readenv=0
#auth       required   pam_env.so readenv=1 envfile=/etc/default/#locale
user_readenv=0
auth       required pam_env.so
auth       sufficient   pam_fprintd.so
auth       sufficient   pam_unix.so try_first_pass likeauth nullok
auth       required pam_deny.so
 <at> include common-auth
 <at> include common-account
 <at> include common-session-noninteractive

end of my config file.
If you want more debugging info, just tell me.
Please help me, I would like to use this hardware when I have it.
Thanks,
vojta
Juvenn Woo | 12 Sep 10:35 2013
Picon

Re: AES3500 problem

Hi gene,

Try to install the following package `libnss3-dev` before you compile. And you may need following packages for compiling fprint_demo:

* libpam0g-dev
* libmagick++-dev
* libusb-1.0-0-dev
* libgtk2.0-dev
* libnss3-dev

FYI, this message is cc'ed to fprint mailing list for future references.


best,
--
jv ♫


On Thu, Sep 12, 2013 at 3:44 PM, Gene Nelms <gnelms1963 <at> yahoo.com> wrote:
Hi Juvenn,

I just located your New Driver for the AES3500 in the Github repository. I am fairly new to Ubuntu. I followed the directions and got the libfprint source patched. But, when I enter the ./autogen.sh  I receive a failure notification because of nss. Shown below. The NSS folder is on my system at this location: /usr/lib/x86_64-linux-gnu

Could you please advise me how to make the necessary changes to complete the driver installation?

Thank you very much for your time..

Gene



gene <at> gene:~/Desktop/makingfprint/libfprint/v_0_5_1$ ./autogen.sh
libtoolize: putting auxiliary files in `.'.
libtoolize: copying file `./ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'.
libtoolize: copying file `m4/libtool.m4'
libtoolize: copying file `m4/ltoptions.m4'
libtoolize: copying file `m4/ltsugar.m4'
libtoolize: copying file `m4/ltversion.m4'
libtoolize: copying file `m4/lt~obsolete.m4'
configure: WARNING: unrecognized options: --enable-maintainer-mode
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking how to print strings... printf
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking how to convert x86_64-unknown-linux-gnu file names to x86_64-unknown-linux-gnu format... func_convert_file_noop
checking how to convert x86_64-unknown-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver <at> FILE support... <at>
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for mt... mt
checking if mt is a manifest tool... no
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for inline... inline
checking whether gcc and cc understand -c and -o together... yes
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking for ld used by g++... /usr/bin/ld -m elf_x86_64
checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC -DPIC
checking if g++ PIC flag -fPIC -DPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking if g++ supports -c -o file.o... (cached) yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking dynamic linker characteristics... (cached) GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for LIBUSB... yes
checking for CRYPTO... no
configure: error: Package requirements (nss) were not met:

No package 'nss' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables CRYPTO_CFLAGS
and CRYPTO_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
-------------------------------------------------------------------




# merge the diff into the master branch of libfprint # and install libfprint (default to /usr/local/) $ cd libfprint $ git apply ../aes3500/src/aes3500.diff $ ./autogen.sh $ make $ sudo make install # build and install fprint_demo $ cd ../fprint_demo $ ./autogen.sh $ ./configure PKG_CONFIG_PATH=/usr/local:$PKG_CONFIG_PATH $ make $ sudo make install # everything is ready and try it with fprint_demo $ sudo fprint_demo


_______________________________________________
fprint mailing list
fprint <at> lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/fprint
Linos | 30 Aug 11:21 2013
Picon

DigitalPersona UareU 5160, work?

Hello,
	i want to update some Upek eikon II that are failing to a new reader,
searching this list and the website it seems that UareU 4500b should
work, but did someone tested the new 5160 model? it's FIPS 201 PIV
certified.

another suggestion? I have 5 units being used in a warehouse by many
different people, i need identification from a list of fingerprints too,
not only verification, given it's used in a warehouse i would like the
reader to be highly durable. Thanks!

Regards,
Miguel Angel.
Javier Domingo | 29 Aug 12:47 2013
Picon

VFS 451

Hi,

Is there any new about VFS451 reader? There is an ubuntu bug about this fingerprint, with people willing to give more traces.

Cheers,

_______________________________________________
fprint mailing list
fprint <at> lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/fprint
Richard Allen | 15 Aug 19:08 2013
Picon

VFS471

Hello all,

I have a "Validity Sensors, Inc. VFS471 Fingerprint Reader" in my laptop.  It's not supported by libfprint.
Going over the code I see there is a vfs301 driver available.

Is there any change the vfs301 driver can be convinced to work with tbe vfs471?   After all, both are from the
same manufacturer and on an USB connection to the host.   Or am I just crazy? :)

--
Rikki
Ricardo Ribalda Delgado | 14 Aug 18:30 2013
Picon

[PATCH] upeke2: Add one more stage to the enrollment

On: ID 147e:2016 Upek Biometric Touchchip/Touchstrip Fingerprint Sensor

The library fails to enroll due to a missing enrolling stage.

upeke2:debug [__handle_incoming_msg] A=00 B=40 len=20
upeke2:debug [__handle_incoming_msg] device responds to subcmd 0 with 14 bytes
upeke2:debug [e_handle_resp00] poll result = 0c
upeke2:debug [alloc_send_cmd28_transfer] seq=50 subcmd=00 with 2 bytes of data
upeke2:debug [__handle_incoming_msg] A=00 B=50 len=20
upeke2:debug [__handle_incoming_msg] device responds to subcmd 0 with 14 bytes
upeke2:debug [e_handle_resp00] poll result = 0c
upeke2:debug [alloc_send_cmd28_transfer] seq=60 subcmd=00 with 2 bytes of data
upeke2:debug [__handle_incoming_msg] A=00 B=60 len=20
upeke2:debug [__handle_incoming_msg] device responds to subcmd 0 with 14 bytes
upeke2:debug [e_handle_resp00] poll result = 0c
upeke2:debug [alloc_send_cmd28_transfer] seq=70 subcmd=00 with 2 bytes of data
upeke2:debug [__handle_incoming_msg] A=00 B=70 len=20
upeke2:debug [__handle_incoming_msg] device responds to subcmd 0 with 14 bytes
upeke2:debug [e_handle_resp00] poll result = 0c
upeke2:debug [alloc_send_cmd28_transfer] seq=80 subcmd=00 with 2 bytes of data
upeke2:debug [__handle_incoming_msg] A=00 B=80 len=20
upeke2:debug [__handle_incoming_msg] device responds to subcmd 0 with 14 bytes
upeke2:debug [e_handle_resp00] poll result = 0c
upeke2:debug [alloc_send_cmd28_transfer] seq=90 subcmd=00 with 2 bytes of data
upeke2:debug [__handle_incoming_msg] A=00 B=90 len=20
upeke2:debug [__handle_incoming_msg] device responds to subcmd 0 with 14 bytes
upeke2:debug [e_handle_resp00] poll result = 20
upeke2:debug [alloc_send_cmd28_transfer] seq=a0 subcmd=00 with 2 bytes of data
upeke2:debug [__handle_incoming_msg] A=00 B=a0 len=20
upeke2:debug [__handle_incoming_msg] device responds to subcmd 0 with 14 bytes
upeke2:debug [e_handle_resp00] poll result = 2e
async:debug [fpi_drvcb_enroll_stage_completed] result 3
sync:debug [sync_enroll_cb] result 3
upeke2:debug [alloc_send_cmd28_transfer] seq=b0 subcmd=00 with 2 bytes of data
sync:debug [fp_enroll_finger_img] enroll stage passed
Enroll stage passed. Yay!

Scan your finger now.
sync:debug [fp_enroll_finger_img]
sync:error [fp_enroll_finger_img] exceeding number of enroll stages for device claimed by driver
upeke2 (5 stages)
sync:debug [fp_enroll_finger_img] ending enrollment
async:debug [fp_async_enroll_stop]
drv:debug [__ssm_call_handler] 0x17762a0 entering state 0
upeke2:debug [alloc_send_cmdresponse_transfer] seq=07 len=1
upeke2:debug [__handle_incoming_msg] A=00 B=b0 len=20
upeke2:debug [__handle_incoming_msg] device responds to subcmd 0 with 14 bytes
upeke2:debug [e_handle_resp00] poll result = 0c
upeke2:debug [alloc_send_cmd28_transfer] seq=c0 subcmd=00 with 2 bytes of data
drv:debug [__ssm_call_handler] 0x17762a0 entering state 1
upeke2:error [read_msg_cb] async msg read failed, code 2
drv:debug [fpi_ssm_mark_aborted] error -1 from state 1
drv:debug [fpi_ssm_mark_completed] 0x17762a0 completed with status -1
async:debug [fpi_drvcb_enroll_stopped]
sync:debug [enroll_stop_cb]
Enroll failed with error -22
sync:debug [fp_dev_close]
async:debug [fpi_drvcb_close_complete]
sync:debug [sync_close_cb]
fp:debug [fp_exit]

Signed-off-by: Ricardo Ribalda Delgado <ricardo.ribalda <at> gmail.com>
---
 libfprint/drivers/upeke2.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/libfprint/drivers/upeke2.c b/libfprint/drivers/upeke2.c
index a7db54d..6c9a56d 100644
--- a/libfprint/drivers/upeke2.c
+++ b/libfprint/drivers/upeke2.c
 <at>  <at>  -874,7 +874,7  <at>  <at>  static int dev_init(struct fp_dev *dev, unsigned long driver_data)
 	upekdev = g_malloc(sizeof(*upekdev));
 	upekdev->seq = 0xf0; /* incremented to 0x00 before first cmd */
 	dev->priv = upekdev;
-	dev->nr_enroll_stages = 5;
+	dev->nr_enroll_stages = 6;

 	fpi_drvcb_open_complete(dev, 0);
 	return 0;
--

-- 
1.7.10.4
Bastien Nocera | 11 Aug 18:29 2013
Picon

libfprint and fprintd 0.5.1 releases

Both available in the usual location:
http://people.freedesktop.org/~hadess/

libfprint changes:
http://cgit.freedesktop.org/libfprint/libfprint/tree/NEWS?id=9e2f8b5e754bf57fe0379428e7a382dacda165fe
fprintd changes:
http://cgit.freedesktop.org/libfprint/fprintd/tree/NEWS?id=3330b8f3513aefbae9088dc8318ab94166b122ad

Next version will include image manipulation using Pixman instead of
gdk-pixbuf and a couple of new drivers.

Cheers
rohan vichare | 7 Aug 13:51 2013
Picon

using libfprint with own driver ( the driver which is not included in the libfprints support)

Dear sir,

i have developed one driver to work with my USB finger print device. which is working fine and i wanted to use the fantastic libfprint for the image processing part can it be used with my ready image data (from driver),
i want to use the function like binarization, minutiae, and verify

please do reply and it will great if i can get any of the code reference for the same,


Thanks & Regards
Rohaan
_______________________________________________
fprint mailing list
fprint <at> lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/fprint
Mike Simpson | 17 Jul 11:34 2013
Picon

Re: fprint Digest, Vol 26, Issue 1



On 14 Jul 2013, at 20:00, fprint-request <at> lists.freedesktop.org wrote:

Send fprint mailing list submissions to
   fprint <at> lists.freedesktop.org

To subscribe or unsubscribe via the World Wide Web, visit
   http://lists.freedesktop.org/mailman/listinfo/fprint
or, via email, send a message with subject or body 'help' to
   fprint-request <at> lists.freedesktop.org

You can reach the person managing the list at
   fprint-owner <at> lists.freedesktop.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of fprint digest..."


Today's Topics:

  1. fingerprints as a crypto key? (Brian J. Murrell)
  2. Re: fingerprints as a crypto key? (Pavel Herrmann)


----------------------------------------------------------------------

Message: 1
Date: Sat, 13 Jul 2013 22:45:24 -0400
From: "Brian J. Murrell" <brian <at> interlinx.bc.ca>
To: fprint <at> lists.freedesktop.org
Subject: [fprint] fingerprints as a crypto key?
Message-ID: <51E210C4.4020501 <at> interlinx.bc.ca>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

I opened bug 66881 about this but I wonder if discussion on the list is
more appropriate so here goes...

I wonder what the general consensus is about using fingerprints to
[un]lock a password store.  Is there enough information in a fingerprint
to provide a decent level of cryptographic security?



Some research in this area. Based on iris scanners but the principle is the same

Problems include false negatives locking you out
- we use fingerprint recognition for identifying patients in order to dispense controlled drugs to them daily but we need to relearn their prints every couple of months and use a stored photo of the patient as a second identifier for the dispenser

And 
If you have your machine compromised and your fingerprint image hash stolen then how do you revoke that "key"

The paper above was written in conjunction with Professor Ross Anderson, author of "Security Engineering" and may be if interest to you

Mike
_______________________________________________
fprint mailing list
fprint <at> lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/fprint

Gmane