From anonymity.m at gmail.com Tue Feb 1 16:41:41 2011 From: anonymity.m at gmail.com (=?GB2312?B?xLjX07Cy?=) Date: Wed, 2 Feb 2011 00:41:41 +0800 Subject: [fprint] Enroll failed with error -22 In-Reply-To: References: <4D41EDD1.1020707@gmail.com> <4D41F541.7080607@lodge.glasgownet.com> <4D42C12E.9010807@gmail.com> <1296486169.7756.10.camel@novo.hadess.net> <4D46D061.10703@lodge.glasgownet.com> <1296487338.7756.12.camel@novo.hadess.net> Message-ID: i have the same problem.so i don't know the app is installed all right... 2011/2/1 miguel G?mez gonzalez : > > I succesfully installed the v_0_3_0 > > my system is a 64 bits, the .configure? install everything under /usr/lib > and not under /usr/lib64, so at the time i try to install pam_fprint it says > libfprint is not installed. also i need to install the libfprint_devel in > order to finishes the make install,? and this package i have only found it > under the yum repositories which is : > > libfprint-devel-0.1.0-19.pre2.el6.x86_64 > > pam_fprint_enroll? it asks now for my fingerprints, i scan it 5 times, and > then sends the follow: > > Found device claimed by UPEK Eikon 2 driver > Opened device. It's now time to enroll your finger. > > You will need to successfully scan your Right Index Finger 5 times to > complete the process. > > Scan your finger now. > Enroll stage passed. Yay! > > Scan your finger now. > Enroll stage passed. Yay! > > Scan your finger now. > Enroll stage passed. Yay! > > Scan your finger now. > Enroll stage passed. Yay! > > Scan your finger now. > Enroll stage passed. Yay! > > Scan your finger now. > Enroll failed with error -22 > wing message: > > > > > > > Mike > > > >> From: hadess at hadess.net >> To: kyle at lodge.glasgownet.com >> Date: Mon, 31 Jan 2011 15:22:17 +0000 >> CC: fprint at reactivated.net >> Subject: Re: [fprint] Enroll failed with error -22 >> >> On Mon, 2011-01-31 at 15:08 +0000, Kyle Gordon wrote: >> > On 31/01/11 15:02, Bastien Nocera wrote: >> > > On Mon, 2011-01-31 at 06:58 -0800, miguel G?mez gonzalez wrote: >> > >> Hi Hugo >> > >> >> > >> Thanks for your quick reply. >> > >> >> > >> I went to the link below and downloaded v_0_3_0.tar.gz , untar it >> > >> and found no configure file, even reading the INSTALL file says to >> > >> run ./configure, make and makeinstall. am i missing something here? >> > >> did i download the correct file? >> > > No, tarballs are at: >> > > http://people.freedesktop.org/~hadess/ >> > > >> > > FWIW, I'd appreciate it if people actually tried to read the >> > > mailing-list archives before making comments, or asking simple >> > > questions >> > > like where to download the latest versions. >> > > >> > > Cheers >> > >> > Why not update your website then? >> >> http://thread.gmane.org/gmane.linux.fprint/1529 >> >> "and I'll be updating the reactivated.net Wiki as soon as Daniel gives >> me >> access to it." >> >> And I still don't have access to it. >> >> _______________________________________________ >> fprint mailing list >> fprint at reactivated.net >> http://lists.reactivated.net/mailman/listinfo/fprint > > _______________________________________________ > fprint mailing list > fprint at reactivated.net > http://lists.reactivated.net/mailman/listinfo/fprint > > From n.shatokhin at gmail.com Wed Feb 2 01:12:37 2011 From: n.shatokhin at gmail.com (=?KOI8-R?B?7snLz8zByiD7wdTPyMnO?=) Date: Wed, 2 Feb 2011 03:12:37 +0200 Subject: [fprint] Buildung libfrint for windows and macos Message-ID: Hello. How to build libfprint for this systems? I installed all depencies, configured IDE, but I can't run configure script, so I don't have file config.h and can't build library. What can I do? Best regards, Nick From alexpro at homelan.lg.ua Sun Feb 6 16:31:27 2011 From: alexpro at homelan.lg.ua (=?koi8-r?Q?=E1=CC=C5=CB=D3=C5=CA_=F0=D2=CF=CB=CF=D0=DE=D5=CB?=) Date: Sun, 6 Feb 2011 18:31:27 +0200 (EET) Subject: [fprint] Writing driver for Egistec reader (1c7a:0801) In-Reply-To: <1174.192.168.200.22.1296080129.squirrel@webmail.homelan.lg.ua> References: <1174.192.168.200.22.1296080129.squirrel@webmail.homelan.lg.ua> Message-ID: <53227.192.168.200.55.1297009887.squirrel@webmail.homelan.lg.ua> I was able to repeat the protocol of data exchange fingerprint reader in a standalone application. Of course, I could not entirely parse the protocol, and I just copied all the actions performed by the driver under Windows. At the moment I can initialize the device and wait for when the fingerprint will be enrolled and then get the data from the reader. The scanner gives the data of the fingerprint by eight blocks of 61440 bytes in each. Manufacturer's web site indicated that image resolution is 192 x 8 pixels @ 508 dpi, 16 gray levels / sensor pixel (4-bit ADC). Unfortunately, I'm totally not familiar with the image processing algorithms. I tried to write the obtained data as the PGM image, but this format only supports 8 bits per pixel, hence 61440 bytes - it is exactly an image 192 x 320. If I give a link to a sample of the data, obtained from reader, can you help me deal with what to do with this data? I would like to know at least what they look like and how they can be passed to the processing libfprint, if it possible at all. Thanks in advance, with best regards, Alexey Prokopchuk. From anarsoul at gmail.com Sun Feb 6 18:05:21 2011 From: anarsoul at gmail.com (Vasily Khoruzhick) Date: Sun, 6 Feb 2011 20:05:21 +0200 Subject: [fprint] Writing driver for Egistec reader (1c7a:0801) In-Reply-To: <53227.192.168.200.55.1297009887.squirrel@webmail.homelan.lg.ua> References: <1174.192.168.200.22.1296080129.squirrel@webmail.homelan.lg.ua> <53227.192.168.200.55.1297009887.squirrel@webmail.homelan.lg.ua> Message-ID: <201102062005.22307.anarsoul@gmail.com> On Sunday 06 February 2011 18:31:27 ??????? ????????? wrote: > I was able to repeat the protocol of data exchange fingerprint reader in a > standalone application. Of course, I could not entirely parse the > protocol, and I just copied all the actions performed by the driver under > Windows. At the moment I can initialize the device and wait for when the > fingerprint will be enrolled and then get the data from the reader. > The scanner gives the data of the fingerprint by eight blocks of 61440 > bytes in each. Manufacturer's web site indicated that image resolution is > 192 x 8 pixels @ 508 dpi, 16 gray levels / sensor pixel (4-bit ADC). > Unfortunately, I'm totally not familiar with the image processing > algorithms. I tried to write the obtained data as the PGM image, but this > format only supports 8 bits per pixel, hence 61440 bytes - it is exactly > an image 192 x 320. > If I give a link to a sample of the data, obtained from reader, can you > help me deal with what to do with this data? I would like to know at least > what they look like and how they can be passed to the processing > libfprint, if it possible at all. > > Thanks in advance, with best regards, Alexey Prokopchuk. Hi, take a look at aes2501 driver, it receives similar parts from sensor, and then assembles them into one image. AFAIK assembling part was separated in common part of aes2501 and aes1610 drivers. Regards Vasily From alexpro at homelan.lg.ua Sun Feb 6 19:22:22 2011 From: alexpro at homelan.lg.ua (=?koi8-r?Q?=E1=CC=C5=CB=D3=C5=CA_=F0=D2=CF=CB=CF=D0=DE=D5=CB?=) Date: Sun, 6 Feb 2011 21:22:22 +0200 (EET) Subject: [fprint] Writing driver for Egistec reader (1c7a:0801) In-Reply-To: <201102062005.22307.anarsoul@gmail.com> References: <1174.192.168.200.22.1296080129.squirrel@webmail.homelan.lg.ua> <53227.192.168.200.55.1297009887.squirrel@webmail.homelan.lg.ua> <201102062005.22307.anarsoul@gmail.com> Message-ID: <48935.192.168.200.55.1297020142.squirrel@webmail.homelan.lg.ua> > Hi, take a look at aes2501 driver, it receives similar parts from sensor, > and > then assembles them into one image. AFAIK assembling part was separated in > common part of aes2501 and aes1610 drivers. > > Regards > Vasily I think, algorithm from this driver is not suitable for me, unfortunately. There is variable count of strips, that have variable length (as I understand from code and comments). In my case - we have fixed count of frames (always 8) fixed length each (always 61440). Data with such size can contain full fingerprint image... When I look at PGM image created from received data, they look very strange. Like some kind of 3D dunes in the desert, if you look at them from the top. But these "dunes" very large relative to size of image, and very different from the fingerprint image. And last one or two images (depending of finger sweeping speed) always almost black. And another problem - my English is too bad for explain more clearly exactly what I want to explain... Lookig to the name at your signature, I suggest that you can speak my native language. If you know something about image processing, can I mail you? In any case, thanks for a tip! :) Regards, Alexey Prokopchuk. From accensi at gmail.com Sun Feb 6 20:59:08 2011 From: accensi at gmail.com (A. C. Censi) Date: Sun, 6 Feb 2011 18:59:08 -0200 Subject: [fprint] Writing driver for Egistec reader (1c7a:0801) In-Reply-To: <48935.192.168.200.55.1297020142.squirrel@webmail.homelan.lg.ua> References: <1174.192.168.200.22.1296080129.squirrel@webmail.homelan.lg.ua> <53227.192.168.200.55.1297009887.squirrel@webmail.homelan.lg.ua> <201102062005.22307.anarsoul@gmail.com> <48935.192.168.200.55.1297020142.squirrel@webmail.homelan.lg.ua> Message-ID: Post the images in, for example, pastebin.com, and give the link. If possible post a photo, taken with a webcam or cell phone camera, of the finger to see the general appearance of the image. It seems that the final fingerprint image will be 192x320 pixels, with 8 bits of data per pixel, to give the gray levels of the pixel. One possible way of decode is that each one of the files correspond all to the same bit of the gray levels for all the pixels, as layers. Other arrangements are equally possible. ACC 2011/2/6 ??????? ????????? : >> Hi, take a look at aes2501 driver, it receives similar parts from sensor, >> and >> then assembles them into one image. AFAIK assembling part was separated in >> common part of aes2501 and aes1610 drivers. >> >> Regards >> Vasily > I think, algorithm from this driver is not suitable for me, unfortunately. > There is variable count of strips, that have variable length (as I > understand from code and comments). In my case - we have fixed count of > frames (always 8) fixed length each (always 61440). Data with such size > can contain full fingerprint image... > When I look at PGM image created from received data, they look very > strange. Like some kind of 3D dunes in the desert, if you look at them > from the top. But these "dunes" very large relative to size of image, and > very different from the fingerprint image. And last one or two images > (depending of finger sweeping speed) always almost black. > And another problem - my English is too bad for explain more clearly > exactly what I want to explain... > > Lookig to the name at your signature, I suggest that you can speak my > native language. If you know something about image processing, can I mail > you? > > In any case, thanks for a tip! :) > > Regards, Alexey Prokopchuk. > > > > _______________________________________________ > fprint mailing list > fprint at reactivated.net > http://lists.reactivated.net/mailman/listinfo/fprint > -- A. C. Censi accensi [em] gmail [ponto] com accensi [em] montreal [ponto] com [ponto] br From cloos at jhcloos.com Sun Feb 6 21:01:34 2011 From: cloos at jhcloos.com (James Cloos) Date: Sun, 06 Feb 2011 16:01:34 -0500 Subject: [fprint] Writing driver for Egistec reader (1c7a:0801) In-Reply-To: <53227.192.168.200.55.1297009887.squirrel@webmail.homelan.lg.ua> (=?utf-8?B?ItCQ0LvQtdC60YHQtdC5INCf0YDQvtC60L7Qv9GH0YPQuiIncw==?= message of "Sun, 6 Feb 2011 18:31:27 +0200 (EET)") References: <1174.192.168.200.22.1296080129.squirrel@webmail.homelan.lg.ua> <53227.192.168.200.55.1297009887.squirrel@webmail.homelan.lg.ua> Message-ID: >>>>> "??" == ??????? ????????? writes: ??> The scanner gives the data of the fingerprint by eight blocks of ??> 61440 bytes in each. Manufacturer's web site indicated that image ??> resolution is 192 x 8 pixels @ 508 dpi, 16 gray levels / sensor ??> pixel (4-bit ADC). Unfortunately, I'm totally not familiar with the ??> image processing algorithms. I tried to write the obtained data as ??> the PGM image, but this format only supports 8 bits per pixel, hence ??> 61440 bytes - it is exactly an image 192 x 320. You might try outputting ascii pgm files; use P2 instead of P5 as the header line, then a line with the width and height output in %d printf(3) format, then a line with the maximum value (15 for a 4-bit int) and then a whitespace-separated list of the 4-bit values in %d format. Eg, something like: P2 6 4 15 0 0 0 0 0 7 0 13 0 4 0 0 0 0 12 0 3 0 8 0 0 11 1 0 At 192 x 8 x 4 bits per stripe you should get 80 stripes out of a 61440 octet blob. ??> If I give a link to a sample of the data, obtained from reader, can ??> you help me deal with what to do with this data? I wouldn't mind trying it out. -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6 From alexpro at homelan.lg.ua Mon Feb 7 01:17:27 2011 From: alexpro at homelan.lg.ua (=?koi8-r?Q?=E1=CC=C5=CB=D3=C5=CA_=F0=D2=CF=CB=CF=D0=DE=D5=CB?=) Date: Mon, 7 Feb 2011 03:17:27 +0200 (EET) Subject: [fprint] Writing driver for Egistec reader (1c7a:0801) In-Reply-To: References: <1174.192.168.200.22.1296080129.squirrel@webmail.homelan.lg.ua> <53227.192.168.200.55.1297009887.squirrel@webmail.homelan.lg.ua> Message-ID: <58340.192.168.200.16.1297041447.squirrel@webmail.homelan.lg.ua> > You might try outputting ascii pgm files; use P2 instead of P5 as the > header line, then a line with the width and height output in %d printf(3) > format, then a line with the maximum value (15 for a 4-bit int) and then > a whitespace-separated list of the 4-bit values in %d format. > > Eg, something like: > > P2 > 6 4 > 15 > 0 0 0 0 0 7 > 0 13 0 4 0 0 > 0 0 12 0 3 0 > 8 0 0 11 1 0 Thanks, I'll try it. >> If I give a link to a sample of the data, obtained from reader, can >> you help me deal with what to do with this data? > > I wouldn't mind trying it out. Enrolled data can be downloaded from here: http://gentoo.homelan.lg.ua/distrib/enroll.tar.bz2 With my very bad English, I'll try to explain all what I can discover... Description of enrolling process on the egistec reader. During the wait loop, when finger sweep detected (changed first byte of a returned buffer), the following occurs: -> send command (I call it "prepare to get data") <- received 6144+13 bytes of data (saved as pre-enroll.bin) -> send command for get image data -> received 61440+13 bytes of data (image 0, saved ad enroll0.bin) And so on seven times again. Last 13 bytes of data appended to all returned buffers independently of the purpose. These 13 bytes always identical in all cases, except errors. I think this some report about operation succeeded. There is two directories in archive - 'slower-sweep' and 'faster-sweep'. Each directory contains pre-enroll data (6144) and 8 saved buffers. Thanks for agreeing to help :) From petr.jakes at tpc.cz Mon Feb 7 01:44:24 2011 From: petr.jakes at tpc.cz (=?UTF-8?Q?Petr_Jake=C5=A1?=) Date: Mon, 7 Feb 2011 02:44:24 +0100 Subject: [fprint] basic access authentication (not PAM!!!) Message-ID: Hi, I would like to know, if it is possible to use libfprint for the simple basic access authentication (not PAM!!!) as described below. - I would like to scan different fingers and store them in to the database - later on, I would like to check if new scanned finger matches against the fingers recorded in the database Thanks for your comments. Best regards Petr Jakes PS: I am able to write the code in the Python and extend it with C or C++ PS: I have installed libfprint 0.3.0 from the git, fprint_demo and pam_fprint_enroll are working OK with my Upek 147e:2016 device. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.reactivated.net/pipermail/fprint/attachments/20110207/b88a9918/attachment.html From hadess at hadess.net Mon Feb 7 13:54:37 2011 From: hadess at hadess.net (Bastien Nocera) Date: Mon, 07 Feb 2011 13:54:37 +0000 Subject: [fprint] basic access authentication (not PAM!!!) In-Reply-To: References: Message-ID: <1297086878.4223.13.camel@novo.hadess.net> On Mon, 2011-02-07 at 02:44 +0100, Petr Jake? wrote: > Hi, > > I would like to know, if it is possible to use libfprint for the > simple basic access authentication (not PAM!!!) as described below. > * I would like to scan different fingers and store them in to > the database > * later on, I would like to check if new scanned finger matches > against the fingers recorded in the database > Thanks for your comments. That's the sort of authentication available in fprintd, to create applications on top of fingerprint readers. Documentation for the D-Bus service are available at: http://people.fedoraproject.org/~hadess/fprintd/docs/ Cheers > PS: > I am able to write the code in the Python and extend it with C or C++ > PS: I have installed libfprint 0.3.0 from the git, fprint_demo and > pam_fprint_enroll are working OK with my Upek 147e:2016 device. > _______________________________________________ > fprint mailing list > fprint at reactivated.net > http://lists.reactivated.net/mailman/listinfo/fprint From petr.jakes at tpc.cz Mon Feb 7 15:52:04 2011 From: petr.jakes at tpc.cz (=?UTF-8?Q?Petr_Jake=C5=A1?=) Date: Mon, 7 Feb 2011 16:52:04 +0100 Subject: [fprint] basic access authentication (not PAM!!!) In-Reply-To: <1297086878.4223.13.camel@novo.hadess.net> References: <1297086878.4223.13.camel@novo.hadess.net> Message-ID: > That's the sort of authentication available in fprintd, to create > applications on top of fingerprint readers. Documentation for the D-Bus > service are available at: > http://people.fedoraproject.org/~hadess/fprintd/docs/ > > Cheers > > I have Installed fprintd from Ubuntu packages (0.2.0+git20101109-0ppa2~maverick1 thanks David). I can see the device using following Python code: myFprint = bus.get_object("net.reactivated.Fprint","/net/reactivated/Fprint/Manager","net.reactivated.Fprint.Manager") print myFprint.GetDevices() print myFprint.GetDefaultDevice() root at korzar-ubuntu:~/automat/automat_swiss# python pokusy.py dbus.Array([dbus.ObjectPath('/net/reactivated/Fprint/Device/0')], signature=dbus.Signature('o')) /net/reactivated/Fprint/Device/0 As far as good. ===================================================== The problem is, I am not able to get any method from the http://hadess.fedorapeople.org/fprintd/docs/Device.html get to work For example the code: scanner = bus.get_object("net.reactivated.Fprint","/net/reactivated/Fprint/Device","net.reactivated.Fprint.Device") scanner.ListEnrolledFingers("petr") throws following error: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.UnknownMethod: Method "ListEnrolledFingers" with signature "s" on interface "(null)" doesn't exist Thanks for your hints. Petr -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.reactivated.net/pipermail/fprint/attachments/20110207/03b9eb5c/attachment.html From hadess at hadess.net Mon Feb 7 16:03:38 2011 From: hadess at hadess.net (Bastien Nocera) Date: Mon, 07 Feb 2011 16:03:38 +0000 Subject: [fprint] basic access authentication (not PAM!!!) In-Reply-To: References: <1297086878.4223.13.camel@novo.hadess.net> Message-ID: <1297094619.29885.7.camel@novo.hadess.net> On Mon, 2011-02-07 at 16:52 +0100, Petr Jake? wrote: > > That's the sort of authentication available in fprintd, to > create > applications on top of fingerprint readers. Documentation for > the D-Bus > service are available at: > http://people.fedoraproject.org/~hadess/fprintd/docs/ > > Cheers > > > > I have Installed fprintd from Ubuntu packages (0.2.0 > +git20101109-0ppa2~maverick1 thanks David). > I can see the device using following Python code: The 0.2 packages are ancient. Use 0.3.0 for both libfprint and fprintd. Cheers From petr.jakes at tpc.cz Mon Feb 7 20:50:22 2011 From: petr.jakes at tpc.cz (=?UTF-8?Q?Petr_Jake=C5=A1?=) Date: Mon, 7 Feb 2011 21:50:22 +0100 Subject: [fprint] basic access authentication (not PAM!!!) In-Reply-To: <1297094619.29885.7.camel@novo.hadess.net> References: <1297086878.4223.13.camel@novo.hadess.net> <1297094619.29885.7.camel@novo.hadess.net> Message-ID: > > I have Installed fprintd from Ubuntu packages (0.2.0 > > +git20101109-0ppa2~maverick1 thanks David). > > I can see the device using following Python code: > > The 0.2 packages are ancient. Use 0.3.0 for both libfprint and fprintd. > > Cheers > > Downloaded the dsd-fprintd-4ea1c48.tar.gz from https://github.com/dsd/fprintd Unfortunatelly, no configure file in the source. Am I missing something? Petr -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.reactivated.net/pipermail/fprint/attachments/20110207/93da10e5/attachment-0001.html From hadess at hadess.net Mon Feb 7 21:23:26 2011 From: hadess at hadess.net (Bastien Nocera) Date: Mon, 07 Feb 2011 21:23:26 +0000 Subject: [fprint] basic access authentication (not PAM!!!) In-Reply-To: References: <1297086878.4223.13.camel@novo.hadess.net> <1297094619.29885.7.camel@novo.hadess.net> Message-ID: <1297113807.29885.16.camel@novo.hadess.net> On Mon, 2011-02-07 at 21:50 +0100, Petr Jake? wrote: > > > I have Installed fprintd from Ubuntu packages (0.2.0 > > +git20101109-0ppa2~maverick1 thanks David). > > I can see the device using following Python code: > > > The 0.2 packages are ancient. Use 0.3.0 for both libfprint and > fprintd. > > Cheers > > > Downloaded the dsd-fprintd-4ea1c48.tar.gz from > https://github.com/dsd/fprintd > > Unfortunatelly, no configure file in the source. > > Am I missing something? http://www.mail-archive.com/fprint at reactivated.net/msg01547.html And read the archives for links to git. Cheers From petr.jakes at tpc.cz Mon Feb 7 22:02:38 2011 From: petr.jakes at tpc.cz (=?UTF-8?Q?Petr_Jake=C5=A1?=) Date: Mon, 7 Feb 2011 23:02:38 +0100 Subject: [fprint] basic access authentication (not PAM!!!) In-Reply-To: <1297113807.29885.16.camel@novo.hadess.net> References: <1297086878.4223.13.camel@novo.hadess.net> <1297094619.29885.7.camel@novo.hadess.net> <1297113807.29885.16.camel@novo.hadess.net> Message-ID: > > > Downloaded the dsd-fprintd-4ea1c48.tar.gz from > > https://github.com/dsd/fprintd > > > > Unfortunatelly, no configure file in the source. > > > > Am I missing something? > > http://www.mail-archive.com/fprint at reactivated.net/msg01547.html > > And read the archives for links to git. > > Cheers > The links points to the fprint, not to the fprind..... ???? I have found the last source in http://cgit.freedesktop.org/libfprint/fprintd/ Sucessfuly compiled using autogen.sh (it was necessary to install gtk-doc-tools and libpolkit-gobject-1-dev first) Unfortunatelly the Python script throws the same error: =============== script snippet ===================== import dbus bus = dbus.SystemBus() scanner = bus.get_object("net.reactivated.Fprint","/net/reactivated/Fprint/Device","net.reactivated.Fprint.Device") print scanner.ListEnrolledFingers("petr") =============================================== Exception: ================================================ dbus.exceptions.DBusException: org.freedesktop.DBus.Error.UnknownMethod: Method "ListEnrolledFingers" with signature "s" on interface "(null)" doesn't exist finally, I have tried to ./configure --localstatedir=/var --prefix=/usr --libdir=/usr/lib --sysconfdir=/etc but the same result Cheers Petr -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.reactivated.net/pipermail/fprint/attachments/20110207/db265fef/attachment.html From hadess at hadess.net Mon Feb 7 23:47:40 2011 From: hadess at hadess.net (Bastien Nocera) Date: Mon, 07 Feb 2011 23:47:40 +0000 Subject: [fprint] basic access authentication (not PAM!!!) In-Reply-To: References: <1297086878.4223.13.camel@novo.hadess.net> <1297094619.29885.7.camel@novo.hadess.net> <1297113807.29885.16.camel@novo.hadess.net> Message-ID: <1297122462.29885.20.camel@novo.hadess.net> On Mon, 2011-02-07 at 23:02 +0100, Petr Jake? wrote: > > Downloaded the dsd-fprintd-4ea1c48.tar.gz from > > https://github.com/dsd/fprintd > > > > Unfortunatelly, no configure file in the source. > > > > Am I missing something? > > > http://www.mail-archive.com/fprint at reactivated.net/msg01547.html > > And read the archives for links to git. > > Cheers > > The links points to the fprint, not to the fprind..... ???? Oops. My apologies for that. > I have found the last source in > http://cgit.freedesktop.org/libfprint/fprintd/ > > Sucessfuly compiled using autogen.sh (it was necessary to install > gtk-doc-tools and libpolkit-gobject-1-dev first) > > Unfortunatelly the Python script throws the same error: > > =============== script snippet ===================== > import dbus > bus = dbus.SystemBus() > > scanner = > bus.get_object("net.reactivated.Fprint","/net/reactivated/Fprint/Device","net.reactivated.Fprint.Device") You can't do that. "/net/reactivated/Fprint/Device" isn't the right object path. You need to get the object path from GetDevices or GetDefaultDevice on the net.reactivated.Fprint.Manager interface. So: import dbus bus = dbus.SystemBus() manager = bus.get_object("net.reactivated.Fprint","/net/reactivated/Fprint/Manager", "net.reactivated.Fprint.Manager") device = manager.GetDefaultDevice() scanner = bus.get_object("net.reactivated.Fprint",device,"net.reactivated.Fprint.Device") print scanner.ListEnrolledFingers("hadess") > finally, I have tried to ./configure --localstatedir=/var > --prefix=/usr --libdir=/usr/lib --sysconfdir=/etc > > but the same result If the above snippet fails, make sure that the utilities shipped with fprintd (fprintd-list, etc.) work as expected. Cheers From petr.jakes at tpc.cz Tue Feb 8 13:28:14 2011 From: petr.jakes at tpc.cz (=?UTF-8?Q?Petr_Jake=C5=A1?=) Date: Tue, 8 Feb 2011 14:28:14 +0100 Subject: [fprint] basic access authentication (not PAM!!!) In-Reply-To: <1297122462.29885.20.camel@novo.hadess.net> References: <1297086878.4223.13.camel@novo.hadess.net> <1297094619.29885.7.camel@novo.hadess.net> <1297113807.29885.16.camel@novo.hadess.net> <1297122462.29885.20.camel@novo.hadess.net> Message-ID: > If the above snippet fails, make sure that the utilities shipped with > fprintd (fprintd-list, etc.) work as expected. > > Thanks for the hint. It looks working now. I am able to call: Claim("petr"), EnrollStart("right-index-finger"), EnrollStop(), Release() But I am lost how to connect to the signals and how to read them Petr -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.reactivated.net/pipermail/fprint/attachments/20110208/4deb3a09/attachment.html From hadess at hadess.net Tue Feb 8 14:13:25 2011 From: hadess at hadess.net (Bastien Nocera) Date: Tue, 08 Feb 2011 14:13:25 +0000 Subject: [fprint] basic access authentication (not PAM!!!) In-Reply-To: References: <1297086878.4223.13.camel@novo.hadess.net> <1297094619.29885.7.camel@novo.hadess.net> <1297113807.29885.16.camel@novo.hadess.net> <1297122462.29885.20.camel@novo.hadess.net> Message-ID: <1297174407.29885.27.camel@novo.hadess.net> On Tue, 2011-02-08 at 14:28 +0100, Petr Jake? wrote: > > If the above snippet fails, make sure that the utilities > shipped with > fprintd (fprintd-list, etc.) work as expected. > > Thanks for the hint. It looks working now. > I am able to call: Claim("petr"), EnrollStart("right-index-finger"), > EnrollStop(), Release() > > But I am lost how to connect to the signals and how to read them My Python D-Bus is rubbish, but this should help: http://dbus.freedesktop.org/doc/dbus-python/doc/tutorial.html#receiving-signals Basically def signalReceived(): print "Signal Received" bus.add_signal_receiver(signalReceived, dbus_interface="net.reactivated.fprint", signal_name="mySignal") From alexpro at homelan.lg.ua Tue Feb 8 22:08:15 2011 From: alexpro at homelan.lg.ua (=?koi8-r?Q?=E1=CC=C5=CB=D3=C5=CA_=F0=D2=CF=CB=CF=D0=DE=D5=CB?=) Date: Wed, 9 Feb 2011 00:08:15 +0200 (EET) Subject: [fprint] Writing driver for Egistec reader (1c7a:0801) In-Reply-To: <53227.192.168.200.55.1297009887.squirrel@webmail.homelan.lg.ua> References: <1174.192.168.200.22.1296080129.squirrel@webmail.homelan.lg.ua> <53227.192.168.200.55.1297009887.squirrel@webmail.homelan.lg.ua> Message-ID: <48853.192.168.200.55.1297202895.squirrel@webmail.homelan.lg.ua> I did it! :) I finally realized how get the image from the received data. Perhaps, the explanation will turn chaotic, but I'll try to explain as precisely as possible. On buffer with 61440 bytes length stored an image 192x80. And that's very interesting that the correct pixel is located in the lower four bits of every fourth byte. Moreover, any fourth byte. For example: I can save PGM image with max gray level 15 from 61440 buffer by four ways: char buf[61440]; buf[0]&0x0F, buf[4]&0x0F, buf[8]&0x0F ... buf[1]&0x0F, buf[5]&0x0F, buf[9]&0x0F ... buf[2]&0x0F, buf[6]&0x0F, buf[10]&0x0F ... buf[3]&0x0F, buf[7]&0x0F, buf[11]&0x0F ... As a result, are four almost identical images, visual difference is almost insignificant. On the images very clearly visible the fingerprint. Although it seems to me to invert the colors, so it will be correct: the black lines of the fingerprint on a white background. In the initial buffer all the way around, the white lines on black background. Now when understandable how to convert a raw buffer to the image, another questions arises ... All eight images - a sequence of sweeping finger on the working surface of the scanner. And now it is unclear how to combine the eight images into one that contains a full fingerprint. And what resolution get this picture as a result... And in which format should I send data to the processing libfprint after final assembly of the image? Thanks in advance! From accensi at gmail.com Tue Feb 8 22:50:10 2011 From: accensi at gmail.com (A. C. Censi) Date: Tue, 8 Feb 2011 20:50:10 -0200 Subject: [fprint] Writing driver for Egistec reader (1c7a:0801) In-Reply-To: <48853.192.168.200.55.1297202895.squirrel@webmail.homelan.lg.ua> References: <1174.192.168.200.22.1296080129.squirrel@webmail.homelan.lg.ua> <53227.192.168.200.55.1297009887.squirrel@webmail.homelan.lg.ua> <48853.192.168.200.55.1297202895.squirrel@webmail.homelan.lg.ua> Message-ID: In other swipe livescanners, the images are taken apart some time and each one represents part of the total image with some overlap. See for instance this paper, where one Atmel chip, similar to the Egistec one, is used: http://3dvision.joanneum.at/3DVision/publications-presentations/literature/pdfs/PUB04DIB015.pdf They used a mathematical adjustment to get the registration of the different images of finger as it swipes in the main movement direction but at same time can slide in the lateral direction, to the right or to the left. See fig 3 on paper. The superposition between the images depends upon the swipe speed, so you can get some black lines if you swipe too fast. I think that with the 8 images you can use any graphics software to find the superposition of subsequent images. Unless you swipe very steadily and with constant speed, the superposition will vary between subsequent images. To do it automatically, you can try some mathematical adjustments or the procedure described in the paper. Any way, good work! A C Censi Any way, it is nice that you could get an image without encryption, because this chip can encrypt the data transmitted. See datasheet from Egistec. 2011/2/8 ??????? ????????? : > I did it! :) > I finally realized how get the image from the received data. > Perhaps, the explanation will turn chaotic, but I'll try to explain as > precisely as possible. > On buffer with 61440 bytes length stored an image 192x80. And that's very > interesting that the correct pixel is located in the lower four bits of > every fourth byte. Moreover, any fourth byte. For example: > I can save PGM image with max gray level 15 from 61440 buffer by four ways: > > char buf[61440]; > > buf[0]&0x0F, buf[4]&0x0F, buf[8]&0x0F ... > buf[1]&0x0F, buf[5]&0x0F, buf[9]&0x0F ... > buf[2]&0x0F, buf[6]&0x0F, buf[10]&0x0F ... > buf[3]&0x0F, buf[7]&0x0F, buf[11]&0x0F ... > > As a result, are four almost identical images, visual difference is almost > insignificant. On the images very clearly visible the fingerprint. > Although it seems to me to invert the colors, so it will be correct: the > black lines of the fingerprint on a white background. In the initial > buffer all the way around, the white lines on black background. > > Now when understandable how to convert a raw buffer to the image, another > questions arises ... All eight images - a sequence of sweeping finger on > the working surface of the scanner. And now it is unclear how to combine > the eight images into one that contains a full fingerprint. And what > resolution get this picture as a result... And in which format should I > send data to the processing libfprint after final assembly of the image? > > Thanks in advance! > > > _______________________________________________ > fprint mailing list > fprint at reactivated.net > http://lists.reactivated.net/mailman/listinfo/fprint > -- A. C. Censi accensi [em] gmail [ponto] com accensi [em] montreal [ponto] com [ponto] br From alexpro at homelan.lg.ua Wed Feb 9 01:16:29 2011 From: alexpro at homelan.lg.ua (=?koi8-r?Q?=E1=CC=C5=CB=D3=C5=CA_=F0=D2=CF=CB=CF=D0=DE=D5=CB?=) Date: Wed, 9 Feb 2011 03:16:29 +0200 (EET) Subject: [fprint] Writing driver for Egistec reader (1c7a:0801) In-Reply-To: <1174.192.168.200.22.1296080129.squirrel@webmail.homelan.lg.ua> References: <1174.192.168.200.22.1296080129.squirrel@webmail.homelan.lg.ua> Message-ID: <47206.192.168.200.55.1297214189.squirrel@webmail.homelan.lg.ua> Finally, I realized how to assemble an complete image. Everything was much easier than I thought at first. All that is needed - this is simply to collect all eight received buffer in one common. The result is a correct fingerprint image 192x640. There is no need any Mathematics - I've checked dozens of times by different fingers - everything works properly. Very interesting Scanner - a normal fingerprint image is obtained only if the sweep finger on the scanner fast enough. If slow, a fingerprint obtained is bad. I did not think that all will be so easy. :) But now, the question remains: In which format should I submit the image for processing in libfprint? Now begins the most difficult and interesting part: everything I've done in a standalone application, should be moved into the driver... It would not be so simple as to deal with images, but I'll try. Thank you very much for your help! I hope that soon a list of supported hardware expands to one more device. With best regards, Alexey Prokopchuk (AP8686-RIPE). From alexpro at homelan.lg.ua Wed Feb 9 10:50:41 2011 From: alexpro at homelan.lg.ua (=?koi8-r?Q?=E1=CC=C5=CB=D3=C5=CA_=F0=D2=CF=CB=CF=D0=DE=D5=CB?=) Date: Wed, 9 Feb 2011 12:50:41 +0200 (EET) Subject: [fprint] Writing driver for Egistec reader (1c7a:0801) In-Reply-To: <47206.192.168.200.55.1297214189.squirrel@webmail.homelan.lg.ua> References: <1174.192.168.200.22.1296080129.squirrel@webmail.homelan.lg.ua> <47206.192.168.200.55.1297214189.squirrel@webmail.homelan.lg.ua> Message-ID: <58693.192.168.200.55.1297248641.squirrel@webmail.homelan.lg.ua> > The result is a correct fingerprint image 192x640. Very strange. There is another way to get the picture. Of the total buffer, collected from eight received can make the image 768x640, but in this case it is necessary to save every byte. The image obtained in this case is not as precise as 192x640, but it looks more natural. I can not understand how it turns out that from scanner with the workspace 192x8 I get the image of 768x640? Now it is unclear which variant to use the final realization? I will begin working with the driver, and try both options. Which one is better - that will be applied finally. Best regards, Alexey Prokopchuk (AP8686-RIPE) From petr.jakes at tpc.cz Fri Feb 11 13:12:20 2011 From: petr.jakes at tpc.cz (=?UTF-8?Q?Petr_Jake=C5=A1?=) Date: Fri, 11 Feb 2011 14:12:20 +0100 Subject: [fprint] basic access authentication (not PAM!!!) In-Reply-To: <1297174407.29885.27.camel@novo.hadess.net> References: <1297086878.4223.13.camel@novo.hadess.net> <1297094619.29885.7.camel@novo.hadess.net> <1297113807.29885.16.camel@novo.hadess.net> <1297122462.29885.20.camel@novo.hadess.net> <1297174407.29885.27.camel@novo.hadess.net> Message-ID: > My Python D-Bus is rubbish, but this should help: > > http://dbus.freedesktop.org/doc/dbus-python/doc/tutorial.html#receiving-signals > > Hmm... thanks. After some foolish experiments, below mentioned code looks working somehow... I will really apprecitate, If some pythoneer here can comment it and tel if it is a way to go ##!/usr/bin/env python; ## -*- coding: utf-8 -*- import sys import time import gobject import dbus, dbus.service from dbus.mainloop.glib import DBusGMainLoop dbus_loop=DBusGMainLoop() dbus.set_default_main_loop(dbus_loop) loop = gobject.MainLoop() def scanHandler(state, secondArgument): print state, secondArgument if state == "enroll-completed": loop.quit() elif state == "enroll-disconnected": loop.quit() bus = dbus.SystemBus() manager = bus.get_object("net.reactivated.Fprint","/net/reactivated/Fprint/Manager","net.reactivated.Fprint.Manager") device = manager.GetDefaultDevice() print device scanner = bus.get_object("net.reactivated.Fprint",device,"net.reactivated.Fprint.Device") scanner.connect_to_signal("EnrollStatus", scanHandler) scanner.Claim("petr") scanner.EnrollStart("right-index-finger") loop.run() print scanner.ListEnrolledFingers("petr") scanner.EnrollStop() scanner.Release() -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.reactivated.net/pipermail/fprint/attachments/20110211/c67a556e/attachment.html From cloos at jhcloos.com Fri Feb 11 21:25:00 2011 From: cloos at jhcloos.com (James Cloos) Date: Fri, 11 Feb 2011 16:25:00 -0500 Subject: [fprint] Writing driver for Egistec reader (1c7a:0801) In-Reply-To: <58693.192.168.200.55.1297248641.squirrel@webmail.homelan.lg.ua> (=?utf-8?B?ItCQ0LvQtdC60YHQtdC5INCf0YDQvtC60L7Qv9GH0YPQuiIncw==?= message of "Wed, 9 Feb 2011 12:50:41 +0200 (EET)") References: <1174.192.168.200.22.1296080129.squirrel@webmail.homelan.lg.ua> <47206.192.168.200.55.1297214189.squirrel@webmail.homelan.lg.ua> <58693.192.168.200.55.1297248641.squirrel@webmail.homelan.lg.ua> Message-ID: >>>>> "??" == ??????? ????????? writes: ??> There is another way to get the picture. Of the total buffer, ??> collected from eight received can make the image 768x640, but in ??> this case it is necessary to save every byte. Something like what one gets from (using what you posted)?: :; (echo P5;echo 768 640;echo 15;cat enroll?.bin) >768x640.pgm -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6 From alexpro at homelan.lg.ua Sat Feb 12 10:29:05 2011 From: alexpro at homelan.lg.ua (=?koi8-r?Q?=E1=CC=C5=CB=D3=C5=CA_=F0=D2=CF=CB=CF=D0=DE=D5=CB?=) Date: Sat, 12 Feb 2011 12:29:05 +0200 (EET) Subject: [fprint] Writing driver for Egistec reader (1c7a:0801) In-Reply-To: References: <1174.192.168.200.22.1296080129.squirrel@webmail.homelan.lg.ua> <47206.192.168.200.55.1297214189.squirrel@webmail.homelan.lg.ua> <58693.192.168.200.55.1297248641.squirrel@webmail.homelan.lg.ua> Message-ID: <50927.192.168.200.55.1297506545.squirrel@webmail.homelan.lg.ua> Greetings! > Something like what one gets from (using what you posted)?: > > :; (echo P5;echo 768 640;echo 15;cat enroll?.bin) >768x640.pgm > Yes, it should be like this. You are also working on a driver for this device? Best regards, Alexey Prokopchuk (AP8686-RIPE) From alexpro at homelan.lg.ua Mon Feb 14 04:37:58 2011 From: alexpro at homelan.lg.ua (=?koi8-r?Q?=E1=CC=C5=CB=D3=C5=CA_=F0=D2=CF=CB=CF=D0=DE=D5=CB?=) Date: Mon, 14 Feb 2011 06:37:58 +0200 (EET) Subject: [fprint] Writing driver for Egistec reader (1c7a:0801) In-Reply-To: <1174.192.168.200.22.1296080129.squirrel@webmail.homelan.lg.ua> References: <1174.192.168.200.22.1296080129.squirrel@webmail.homelan.lg.ua> Message-ID: <50411.192.168.200.55.1297658278.squirrel@webmail.homelan.lg.ua> Greetings! The initial version of the driver now is ready. So far I've tested it only with the program 'enroll'in the directory 'examples'. I still do not understand what version of the image will be correct, 192x640 ili 768x640? Links to images of the same finger with different image parameters: 192x640: http://gentoo.homelan.lg.ua/distrib/enrolled1.pgm 768x640: http://gentoo.homelan.lg.ua/distrib/enrolled2.pgm Would like to ask your opinion about what kind of picture is better for libfprint works properly? With best regards, Alexey Prokopchuk (AP8686-RIPE) From sergio.cerlesi at gmail.com Mon Feb 14 08:25:13 2011 From: sergio.cerlesi at gmail.com (sergio cerlesi) Date: Mon, 14 Feb 2011 09:25:13 +0100 Subject: [fprint] fprintd and fpi_timeout_add Message-ID: Hi Daniel, Bastien, i'm working on fprint Validity VFS101 driver. The driver work with fprint_demo and pam_fprint but not with fprintd. The cause of problem is that it call the function fpi_timeout_add that take conflict with fprintd ( the callback is never call). I can't use this function or is a bug of fprintd ? I'm not sure but i think that other drivers like uru4000 can have the same problem. Bye Sergio -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.reactivated.net/pipermail/fprint/attachments/20110214/ef255b4a/attachment.html From hadess at hadess.net Mon Feb 14 08:53:51 2011 From: hadess at hadess.net (Bastien Nocera) Date: Mon, 14 Feb 2011 08:53:51 +0000 Subject: [fprint] fprintd and fpi_timeout_add In-Reply-To: References: Message-ID: <1297673632.2495.1.camel@novo.hadess.net> On Mon, 2011-02-14 at 09:25 +0100, sergio cerlesi wrote: > Hi Daniel, Bastien, > > i'm working on fprint Validity VFS101 driver. The driver work with > fprint_demo and pam_fprint but not with fprintd. > > The cause of problem is that it call the function fpi_timeout_add that > take conflict with fprintd ( the callback is never call). > > I can't use this function or is a bug of fprintd ? > > I'm not sure but i think that other drivers like uru4000 can have the > same problem. Sorry Sergio, but I don't understand what the problem is here... Cheers From sergio.cerlesi at gmail.com Mon Feb 14 09:35:32 2011 From: sergio.cerlesi at gmail.com (sergio cerlesi) Date: Mon, 14 Feb 2011 10:35:32 +0100 Subject: [fprint] fprintd and fpi_timeout_add In-Reply-To: <1297673632.2495.1.camel@novo.hadess.net> References: <1297673632.2495.1.camel@novo.hadess.net> Message-ID: Hi Bastien, at first, sorry for my bad english e if i'm not clear. The problem is that the driver i wrote for device Validity VFS101 work with fprint_demo and pam_fprint but NOT with pam_fprintd. I debug the driver and i find that the cause of problem is a call of function fpi_timeout_add on the driver. Below i report the portion of code that have the problem: /* Callback of asynchronous sleep */ static void async_sleep_cb(void *data) { struct fpi_ssm *ssm = data; fpi_ssm_next_state(ssm); } /* Submit asynchronous sleep */ static void async_sleep(unsigned int msec, struct fpi_ssm *ssm) { if (fpi_timeout_add(msec, async_sleep_cb, ssm) == NULL) fpi_ssm_mark_aborted(ssm, -ETIME); } If i use fprint_demo or pam_fprint for test the driver the callback function are correctly called after timeout and the driver work. If i use pam_fprintd (fprintd-0.2.0) the callback are never called and the driver are blocked. I can't understand if it's a bug of driver or of fprintd. Can you help me ? Bye Sergio 2011/2/14 Bastien Nocera > On Mon, 2011-02-14 at 09:25 +0100, sergio cerlesi wrote: > > Hi Daniel, Bastien, > > > > i'm working on fprint Validity VFS101 driver. The driver work with > > fprint_demo and pam_fprint but not with fprintd. > > > > The cause of problem is that it call the function fpi_timeout_add that > > take conflict with fprintd ( the callback is never call). > > > > I can't use this function or is a bug of fprintd ? > > > > I'm not sure but i think that other drivers like uru4000 can have the > > same problem. > > Sorry Sergio, but I don't understand what the problem is here... > > Cheers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.reactivated.net/pipermail/fprint/attachments/20110214/26f4999d/attachment-0001.html From dan at reactivated.net Mon Feb 14 09:56:17 2011 From: dan at reactivated.net (Daniel Drake) Date: Mon, 14 Feb 2011 09:56:17 +0000 Subject: [fprint] Writing driver for Egistec reader (1c7a:0801) In-Reply-To: <50411.192.168.200.55.1297658278.squirrel@webmail.homelan.lg.ua> References: <1174.192.168.200.22.1296080129.squirrel@webmail.homelan.lg.ua> <50411.192.168.200.55.1297658278.squirrel@webmail.homelan.lg.ua> Message-ID: <4D58FC41.6070908@reactivated.net> > 192x640: > http://gentoo.homelan.lg.ua/distrib/enrolled1.pgm > 768x640: > http://gentoo.homelan.lg.ua/distrib/enrolled2.pgm > > Would like to ask your opinion about what kind of picture is better for > libfprint works properly? Try them both, and see how well they work with the image processing code. Neither of them look ideal - the second one is fuzzy, the first one is vertically stretched. But perhaps it doesn't matter and they already work OK with the image processing code. If not, you have the option of writing some simple code to "unstretch" the first image (go row by row, reject a new row if it is too similar to the previous one, there is similar code in other drivers) Daniel From alexpro at homelan.lg.ua Tue Feb 15 14:43:45 2011 From: alexpro at homelan.lg.ua (=?koi8-r?Q?=E1=CC=C5=CB=D3=C5=CA_=F0=D2=CF=CB=CF=D0=DE=D5=CB?=) Date: Tue, 15 Feb 2011 16:43:45 +0200 (EET) Subject: [fprint] Writing driver for Egistec reader (1c7a:0801) In-Reply-To: <1174.192.168.200.22.1296080129.squirrel@webmail.homelan.lg.ua> References: <1174.192.168.200.22.1296080129.squirrel@webmail.homelan.lg.ua> Message-ID: <57009.192.168.200.50.1297781025.squirrel@webmail.homelan.lg.ua> Greetings! Would like to ask whether the libfprint restrictions on the size of processed images? The fact is that if the image size 768 x 640, then after the fingerprint scanning and saving the image (in 'enroll' program from 'examples' directory) program crash occurs (segmentation fault) in function 'free_minutiaes()'. If image size is 192 x 640 program finished correctly without any problems. Regards, Alexey Prokopchuk (AP8686-RIPE) From sergio.cerlesi at gmail.com Tue Feb 15 15:38:26 2011 From: sergio.cerlesi at gmail.com (sergio cerlesi) Date: Tue, 15 Feb 2011 16:38:26 +0100 Subject: [fprint] fprintd and fpi_timeout_add In-Reply-To: References: <1297673632.2495.1.camel@novo.hadess.net> Message-ID: Hi Daniel, Bastien, i found the bug! On function fp_get_next_timeout of libfprint (file poll.c) if exist fprint timeout or libusb timeout the function return the smaller of the 2 timeout. But if one of that not exist and have a smaller value the function return a timeout that not exist. The attached patch fix the bug. It possible to apply the patch to the library ? Thank Sergio 2011/2/14 sergio cerlesi > Hi Bastien, > > at first, sorry for my bad english e if i'm not clear. > > The problem is that the driver i wrote for device Validity VFS101 work with > fprint_demo and pam_fprint but NOT with pam_fprintd. > > I debug the driver and i find that the cause of problem is a call of > function fpi_timeout_add on the driver. Below i report the portion of code > that have the problem: > > /* Callback of asynchronous sleep */ > static void async_sleep_cb(void *data) > { > struct fpi_ssm *ssm = data; > > fpi_ssm_next_state(ssm); > } > > /* Submit asynchronous sleep */ > static void async_sleep(unsigned int msec, struct fpi_ssm *ssm) > { > if (fpi_timeout_add(msec, async_sleep_cb, ssm) == NULL) > fpi_ssm_mark_aborted(ssm, -ETIME); > } > > If i use fprint_demo or pam_fprint for test the driver the callback > function are correctly called after timeout and the driver work. > If i use pam_fprintd (fprintd-0.2.0) the callback are never called and the > driver are blocked. > > I can't understand if it's a bug of driver or of fprintd. Can you help me ? > > Bye > Sergio > > 2011/2/14 Bastien Nocera > > On Mon, 2011-02-14 at 09:25 +0100, sergio cerlesi wrote: >> > Hi Daniel, Bastien, >> > >> > i'm working on fprint Validity VFS101 driver. The driver work with >> > fprint_demo and pam_fprint but not with fprintd. >> > >> > The cause of problem is that it call the function fpi_timeout_add that >> > take conflict with fprintd ( the callback is never call). >> > >> > I can't use this function or is a bug of fprintd ? >> > >> > I'm not sure but i think that other drivers like uru4000 can have the >> > same problem. >> >> Sorry Sergio, but I don't understand what the problem is here... >> >> Cheers >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.reactivated.net/pipermail/fprint/attachments/20110215/fc6d5efa/attachment.html -------------- next part -------------- A non-text attachment was scrubbed... Name: libfprint-0.3.0-next_timeout.patch Type: application/octet-stream Size: 566 bytes Desc: not available Url : http://lists.reactivated.net/pipermail/fprint/attachments/20110215/fc6d5efa/libfprint-0.3.0-next_timeout.obj From dan at reactivated.net Tue Feb 15 20:22:27 2011 From: dan at reactivated.net (Daniel Drake) Date: Tue, 15 Feb 2011 20:22:27 +0000 Subject: [fprint] fprintd and fpi_timeout_add In-Reply-To: References: <1297673632.2495.1.camel@novo.hadess.net> Message-ID: <4D5AE083.5060907@reactivated.net> > i found the bug! > > On function fp_get_next_timeout of libfprint (file poll.c) if exist > fprint timeout or libusb timeout the function return the smaller of the > 2 timeout. > > But if one of that not exist and have a smaller value the function > return a timeout that not exist. Nice find. The patch looks correct. Daniel From hadess at hadess.net Tue Feb 15 20:47:45 2011 From: hadess at hadess.net (Bastien Nocera) Date: Tue, 15 Feb 2011 20:47:45 +0000 Subject: [fprint] fprintd and fpi_timeout_add In-Reply-To: References: <1297673632.2495.1.camel@novo.hadess.net> Message-ID: <1297802868.2049.6.camel@novo.hadess.net> Hey Sergio, On Tue, 2011-02-15 at 16:38 +0100, sergio cerlesi wrote: > Hi Daniel, Bastien, > > i found the bug! > > On function fp_get_next_timeout of libfprint (file poll.c) if exist > fprint timeout or libusb timeout the function return the smaller of > the 2 timeout. > > But if one of that not exist and have a smaller value the function > return a timeout that not exist. > > The attached patch fix the bug. It possible to apply the patch to the > library ? Good catch. Any chance you could create a git formatted patch so that explanations about the bug it solves, and authorship are kept? Cheers > 2011/2/14 sergio cerlesi > Hi Bastien, > > at first, sorry for my bad english e if i'm not clear. > > The problem is that the driver i wrote for device Validity > VFS101 work with fprint_demo and pam_fprint but NOT with > pam_fprintd. > > I debug the driver and i find that the cause of problem is a > call of function fpi_timeout_add on the driver. Below i report > the portion of code that have the problem: > > /* Callback of asynchronous sleep */ > static void async_sleep_cb(void *data) > { > struct fpi_ssm *ssm = data; > > fpi_ssm_next_state(ssm); > } > > /* Submit asynchronous sleep */ > static void async_sleep(unsigned int msec, struct fpi_ssm > *ssm) > { > if (fpi_timeout_add(msec, async_sleep_cb, ssm) == NULL) > fpi_ssm_mark_aborted(ssm, -ETIME); > } > > If i use fprint_demo or pam_fprint for test the driver the > callback function are correctly called after timeout and the > driver work. > If i use pam_fprintd (fprintd-0.2.0) the callback are never > called and the driver are blocked. > > I can't understand if it's a bug of driver or of fprintd. Can > you help me ? > > Bye > Sergio > > 2011/2/14 Bastien Nocera > > > > On Mon, 2011-02-14 at 09:25 +0100, sergio cerlesi > wrote: > > Hi Daniel, Bastien, > > > > i'm working on fprint Validity VFS101 driver. The > driver work with > > fprint_demo and pam_fprint but not with fprintd. > > > > The cause of problem is that it call the function > fpi_timeout_add that > > take conflict with fprintd ( the callback is never > call). > > > > I can't use this function or is a bug of fprintd ? > > > > I'm not sure but i think that other drivers like > uru4000 can have the > > same problem. > > > Sorry Sergio, but I don't understand what the problem > is here... > > Cheers > > > From sergio.cerlesi at gmail.com Wed Feb 16 10:50:12 2011 From: sergio.cerlesi at gmail.com (Sergio Cerlesi) Date: Wed, 16 Feb 2011 11:50:12 +0100 Subject: [fprint] fprintd and fpi_timeout_add In-Reply-To: <1297802868.2049.6.camel@novo.hadess.net> References: <1297673632.2495.1.camel@novo.hadess.net> <1297802868.2049.6.camel@novo.hadess.net> Message-ID: <1297853412.18795.7.camel@cerlyLp> Hi Bastien, patch attached. Tell me if the format isn't correct. Bye Sergio Il giorno mar, 15/02/2011 alle 20.47 +0000, Bastien Nocera ha scritto: > Hey Sergio, > > On Tue, 2011-02-15 at 16:38 +0100, sergio cerlesi wrote: > > Hi Daniel, Bastien, > > > > i found the bug! > > > > On function fp_get_next_timeout of libfprint (file poll.c) if exist > > fprint timeout or libusb timeout the function return the smaller of > > the 2 timeout. > > > > But if one of that not exist and have a smaller value the function > > return a timeout that not exist. > > > > The attached patch fix the bug. It possible to apply the patch to the > > library ? > > Good catch. Any chance you could create a git formatted patch so that > explanations about the bug it solves, and authorship are kept? > > Cheers > > > 2011/2/14 sergio cerlesi > > Hi Bastien, > > > > at first, sorry for my bad english e if i'm not clear. > > > > The problem is that the driver i wrote for device Validity > > VFS101 work with fprint_demo and pam_fprint but NOT with > > pam_fprintd. > > > > I debug the driver and i find that the cause of problem is a > > call of function fpi_timeout_add on the driver. Below i report > > the portion of code that have the problem: > > > > /* Callback of asynchronous sleep */ > > static void async_sleep_cb(void *data) > > { > > struct fpi_ssm *ssm = data; > > > > fpi_ssm_next_state(ssm); > > } > > > > /* Submit asynchronous sleep */ > > static void async_sleep(unsigned int msec, struct fpi_ssm > > *ssm) > > { > > if (fpi_timeout_add(msec, async_sleep_cb, ssm) == NULL) > > fpi_ssm_mark_aborted(ssm, -ETIME); > > } > > > > If i use fprint_demo or pam_fprint for test the driver the > > callback function are correctly called after timeout and the > > driver work. > > If i use pam_fprintd (fprintd-0.2.0) the callback are never > > called and the driver are blocked. > > > > I can't understand if it's a bug of driver or of fprintd. Can > > you help me ? > > > > Bye > > Sergio > > > > 2011/2/14 Bastien Nocera > > > > > > > > On Mon, 2011-02-14 at 09:25 +0100, sergio cerlesi > > wrote: > > > Hi Daniel, Bastien, > > > > > > i'm working on fprint Validity VFS101 driver. The > > driver work with > > > fprint_demo and pam_fprint but not with fprintd. > > > > > > The cause of problem is that it call the function > > fpi_timeout_add that > > > take conflict with fprintd ( the callback is never > > call). > > > > > > I can't use this function or is a bug of fprintd ? > > > > > > I'm not sure but i think that other drivers like > > uru4000 can have the > > > same problem. > > > > > > Sorry Sergio, but I don't understand what the problem > > is here... > > > > Cheers > > > > > > > > -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Fix-return-timeout-of-fp_get_next_timeout.patch Type: text/x-patch Size: 1166 bytes Desc: not available Url : http://lists.reactivated.net/pipermail/fprint/attachments/20110216/88dcee0e/0001-Fix-return-timeout-of-fp_get_next_timeout-0001.bin From alexpro at homelan.lg.ua Wed Feb 16 12:55:45 2011 From: alexpro at homelan.lg.ua (=?koi8-r?Q?=E1=CC=C5=CB=D3=C5=CA_=F0=D2=CF=CB=CF=D0=DE=D5=CB?=) Date: Wed, 16 Feb 2011 14:55:45 +0200 (EET) Subject: [fprint] Writing driver for Egistec reader (1c7a:0801) In-Reply-To: <1174.192.168.200.22.1296080129.squirrel@webmail.homelan.lg.ua> References: <1174.192.168.200.22.1296080129.squirrel@webmail.homelan.lg.ua> Message-ID: <54917.192.168.200.16.1297860945.squirrel@webmail.homelan.lg.ua> Greetings! It seems I found the best option for the image parameters. 192 x 160 - this is the best result that I could get from a scanner EgisTec SS801U. Program 'verify' and 'verify_live' from the directory 'examples' can recognize my fingerprints. However, it is best recognized the middle finger, index finger did not always recognized. Now I will try to use pam_libfprint for authentication to the system, I think it should be able to. Here's a link to the scan, which can be recognized by libfprint (right index finger): http://gentoo.homelan.lg.ua/distrib/final-enrolled.pgm Now what to do with the the source code of the driver? Which ID of the driver should I use? Now I set ID value equal to 10, the first free for now. Unfortunately, I could not completely understand the communication protocol of this device, in particular the mechanism of its deinitialisation. Therefore, I have to make device reset in the procedure of activation. In any case, the driver is still necessary testing, but I have no this possibility, because I only have one Notebook with such device, and no other one around. With best regards, Alexey Prokopchuk (AP8686-RIPE) From erundook at gmail.com Wed Feb 16 17:22:48 2011 From: erundook at gmail.com (Vitaly Sorokin) Date: Wed, 16 Feb 2011 20:22:48 +0300 Subject: [fprint] Writing driver for Egistec reader (1c7a:0801) Message-ID: Hi Alexey, Im having a laptop with the same fprint reader. I could help testing the driver. Where can I download it and any instructions on using it? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.reactivated.net/pipermail/fprint/attachments/20110216/559568e5/attachment.html From alexpro at homelan.lg.ua Wed Feb 16 23:15:34 2011 From: alexpro at homelan.lg.ua (=?koi8-r?Q?=E1=CC=C5=CB=D3=C5=CA_=F0=D2=CF=CB=CF=D0=DE=D5=CB?=) Date: Thu, 17 Feb 2011 01:15:34 +0200 (EET) Subject: [fprint] Writing driver for Egistec reader (1c7a:0801) In-Reply-To: <54917.192.168.200.16.1297860945.squirrel@webmail.homelan.lg.ua> References: <1174.192.168.200.22.1296080129.squirrel@webmail.homelan.lg.ua> <54917.192.168.200.16.1297860945.squirrel@webmail.homelan.lg.ua> Message-ID: <39375.192.168.200.16.1297898134.squirrel@webmail.homelan.lg.ua> I tried to use pam_libfprint with my new driver for logon with kde-4.5.5. It works, but not so as I expected... pam_libfprint on kdm logon screen always asks same finger, and exspects exactly that finger from me, I can't use any other finger. And pam_libfprint always asks the last enrolled finger. For example - I enrolled right index, middle and ring fingers. pam_libfprint asks for only right ring finger on logon, and no other enrolled fingers accepted. If I delete ring finger image, then pam-libfprint asks for right middle finger. Maybe I don't understand how to use pam_libfprint? Regards, Alexey Prokopchuk (AP8686-RIPE) From morpheus.ibis at gmail.com Wed Feb 16 23:24:30 2011 From: morpheus.ibis at gmail.com (Pavel Herrmann) Date: Thu, 17 Feb 2011 00:24:30 +0100 Subject: [fprint] Writing driver for Egistec reader (1c7a:0801) In-Reply-To: <39375.192.168.200.16.1297898134.squirrel@webmail.homelan.lg.ua> References: <1174.192.168.200.22.1296080129.squirrel@webmail.homelan.lg.ua> <54917.192.168.200.16.1297860945.squirrel@webmail.homelan.lg.ua> <39375.192.168.200.16.1297898134.squirrel@webmail.homelan.lg.ua> Message-ID: <201102170024.30675.morpheus.ibis@gmail.com> On Thursday, February 17, 2011 12:15:34 am ??????? ????????? wrote: > I tried to use pam_libfprint with my new driver for logon with kde-4.5.5. > It works, but not so as I expected... pam_libfprint on kdm logon screen > always asks same finger, and exspects exactly that finger from me, I can't > use any other finger. And pam_libfprint always asks the last enrolled > finger. For example - I enrolled right index, middle and ring fingers. > pam_libfprint asks for only right ring finger on logon, and no other > enrolled fingers accepted. If I delete ring finger image, then > pam-libfprint asks for right middle finger. Maybe I don't understand how > to use pam_libfprint? Hi, can you confirm "identify" works in demo apps? it should work on all image- based scanners, and AFAIK is used by pam_fprint when available and one more thing, pam_fprint or pam_fprintd? this information may be plain wrong or just deprecated, as I have not seen the code since ~0.1.0 Pavel From alexpro at homelan.lg.ua Wed Feb 16 23:45:19 2011 From: alexpro at homelan.lg.ua (=?koi8-r?Q?=E1=CC=C5=CB=D3=C5=CA_=F0=D2=CF=CB=CF=D0=DE=D5=CB?=) Date: Thu, 17 Feb 2011 01:45:19 +0200 (EET) Subject: [fprint] Writing driver for Egistec reader (1c7a:0801) In-Reply-To: <201102170024.30675.morpheus.ibis@gmail.com> References: <1174.192.168.200.22.1296080129.squirrel@webmail.homelan.lg.ua> <54917.192.168.200.16.1297860945.squirrel@webmail.homelan.lg.ua> <39375.192.168.200.16.1297898134.squirrel@webmail.homelan.lg.ua> <201102170024.30675.morpheus.ibis@gmail.com> Message-ID: <52274.192.168.200.16.1297899919.squirrel@webmail.homelan.lg.ua> > Hi, > > can you confirm "identify" works in demo apps? it should work on all > image- > based scanners, and AFAIK is used by pam_fprint when available > > and one more thing, pam_fprint or pam_fprintd? > > this information may be plain wrong or just deprecated, as I have not seen > the > code since ~0.1.0 > > Pavel Yes, I confirm that identify works. I tested it with fprint_demo. Acceptance rate not such as I expected but for the first time is not so bad. I was wrong in the name of the module, I'm sorry. Of course, I used pam_fprint-0.2, installed from ebuild which present in gentoo portage tree, not pam_fprintd. I even never heard about pam_fprintd before. However, I have fprintd-0.2 installed on my system, but I don't know how to use it at all. And, as I said before, I can authenticate with pam_fprint, but it allow to use only one finger for me. From hadess at hadess.net Thu Feb 17 01:49:36 2011 From: hadess at hadess.net (Bastien Nocera) Date: Thu, 17 Feb 2011 01:49:36 +0000 Subject: [fprint] Writing driver for Egistec reader (1c7a:0801) In-Reply-To: <52274.192.168.200.16.1297899919.squirrel@webmail.homelan.lg.ua> References: <1174.192.168.200.22.1296080129.squirrel@webmail.homelan.lg.ua> <54917.192.168.200.16.1297860945.squirrel@webmail.homelan.lg.ua> <39375.192.168.200.16.1297898134.squirrel@webmail.homelan.lg.ua> <201102170024.30675.morpheus.ibis@gmail.com> <52274.192.168.200.16.1297899919.squirrel@webmail.homelan.lg.ua> Message-ID: <1297907377.2049.16.camel@novo.hadess.net> On Thu, 2011-02-17 at 01:45 +0200, ??????? ????????? wrote: > > Hi, > > > > can you confirm "identify" works in demo apps? it should work on all > > image- > > based scanners, and AFAIK is used by pam_fprint when available > > > > and one more thing, pam_fprint or pam_fprintd? > > > > this information may be plain wrong or just deprecated, as I have not seen > > the > > code since ~0.1.0 > > > > Pavel > Yes, I confirm that identify works. I tested it with fprint_demo. > Acceptance rate not such as I expected but for the first time is not so > bad. I was wrong in the name of the module, I'm sorry. Of course, I used > pam_fprint-0.2, installed from ebuild which present in gentoo portage > tree, not pam_fprintd. I even never heard about pam_fprintd before. > However, I have fprintd-0.2 installed on my system, but I don't know how > to use it at all. There's documentation on how to tell PAM to use the pam_fprintd module in the source tree itself. See pam/README. > And, as I said before, I can authenticate with pam_fprint, but it allow to > use only one finger for me. pam_fprint is deprecated. It shouldn't be used. If you have fprintd installed, just run "fprintd-enroll", "fprintd-list" and "fprintd-verify" to test whether fprintd works correctly with the reader. You can also run /usr/libexec/fprintd on its own (as root) if there are any problems to see fprintd's output (make sure you kill any running instances). Cheers From hadess at hadess.net Fri Feb 18 13:59:52 2011 From: hadess at hadess.net (Bastien Nocera) Date: Fri, 18 Feb 2011 13:59:52 +0000 Subject: [fprint] fprintd and fpi_timeout_add In-Reply-To: <1297853412.18795.7.camel@cerlyLp> References: <1297673632.2495.1.camel@novo.hadess.net> <1297802868.2049.6.camel@novo.hadess.net> <1297853412.18795.7.camel@cerlyLp> Message-ID: <1298037594.2049.52.camel@novo.hadess.net> On Wed, 2011-02-16 at 11:50 +0100, Sergio Cerlesi wrote: > Hi Bastien, > > patch attached. Tell me if the format isn't correct. Pushed, thanks! From poehn at online.de Sat Feb 19 08:13:06 2011 From: poehn at online.de (Sebastian =?ISO-8859-1?B?UPZobg==?=) Date: Sat, 19 Feb 2011 09:13:06 +0100 Subject: [fprint] VFS300 Message-ID: <20110219091306.13a49272@Apfel7> Hi! My laptop has a ugly Validity VFS300 (138a:0008) fingerprint reader. The bad guys of Dell (they say: We have a driver, but it will only be shipped with our Ubuntu installation ;-) do not want to give the driver to me. Could somebody please send me a usb sniff of a VFS101? I got the code of rayl and I hope differences between the validity familiy are not to big! Greetings Sebastian From sml-re at gmx.de Mon Feb 21 18:09:13 2011 From: sml-re at gmx.de (Stephan Lange) Date: Mon, 21 Feb 2011 19:09:13 +0100 Subject: [fprint] Support for Identix PCMCIA Message-ID: <1298311753.4d62aa490e83a@gmx.de> Hello, is there or will be there any support for the IDENTIX BTO-30P-GEN-T01 (pccard device)? Thanks in advance, Stephan From sergio.cerlesi at gmail.com Tue Feb 22 14:01:12 2011 From: sergio.cerlesi at gmail.com (Sergio Cerlesi) Date: Tue, 22 Feb 2011 15:01:12 +0100 Subject: [fprint] Fix for fpi_im_resize (gdkpixbuf.c) Message-ID: <1298383272.12678.9.camel@cerlyLp> Hi Bastien, Daniel, i found a lite bug on function fpi_im_resize (gdkpixbuf.c). Instead of copy resized image into newimg, the function copy it on old img so, new image is empty and, in some case, it generated a segmentation fault error. The attached patch fix the function. Bye Sergio -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Fix-function-fpi_im_resize-on-create-new-image.patch Type: text/x-patch Size: 929 bytes Desc: not available Url : http://lists.reactivated.net/pipermail/fprint/attachments/20110222/6aa0f301/0001-Fix-function-fpi_im_resize-on-create-new-image.bin From hadess at hadess.net Tue Feb 22 19:17:08 2011 From: hadess at hadess.net (Bastien Nocera) Date: Tue, 22 Feb 2011 19:17:08 +0000 Subject: [fprint] Fix for fpi_im_resize (gdkpixbuf.c) In-Reply-To: <1298383272.12678.9.camel@cerlyLp> References: <1298383272.12678.9.camel@cerlyLp> Message-ID: <1298402229.3574.0.camel@novo.hadess.net> On Tue, 2011-02-22 at 15:01 +0100, Sergio Cerlesi wrote: > Hi Bastien, Daniel, > > i found a lite bug on function fpi_im_resize (gdkpixbuf.c). > > Instead of copy resized image into newimg, the function copy it on old > img so, new image is empty and, in some case, it generated a > segmentation fault error. > > The attached patch fix the function. Pushed, thanks very much! From sergio.cerlesi at gmail.com Fri Feb 25 08:49:23 2011 From: sergio.cerlesi at gmail.com (Sergio Cerlesi) Date: Fri, 25 Feb 2011 09:49:23 +0100 Subject: [fprint] New driver for Validity VFS101: tester wanted Message-ID: <1298623763.494.16.camel@cerlyLp> Hi all, i finish to write the driver fo Validity VFS101. I use it for a couple of day with good result. For verify the implementation i need tester. If i receive positive feedback i will work to merge it into library. Attached the patch for libfprint 0.3.0. To compile it run: autoreconf && ./configure && make Important: the match score is much variable (on my experience from 10 to 100) so, to have a good chance to match the fingerprint, it's much important who scan is done. I use fprint_demo to find the best way to scan my finger. Waiting feedback. Bye Sergio -------------- next part -------------- A non-text attachment was scrubbed... Name: libfprint-0.3.0-vfs101.patch Type: text/x-patch Size: 34440 bytes Desc: not available Url : http://lists.reactivated.net/pipermail/fprint/attachments/20110225/9f557c27/libfprint-0.3.0-vfs101-0001.bin From surenkarapetyan at gmail.com Fri Feb 25 12:41:25 2011 From: surenkarapetyan at gmail.com (Suren Karapetyan) Date: Fri, 25 Feb 2011 16:41:25 +0400 Subject: [fprint] New driver for Validity VFS101: tester wanted In-Reply-To: <1298623763.494.16.camel@cerlyLp> References: <1298623763.494.16.camel@cerlyLp> Message-ID: <20110225164125.5459aba7@roadrunner.surolan.local> On Fri, 25 Feb 2011 09:49:23 +0100 Sergio Cerlesi wrote: > Hi all, > > i finish to write the driver fo Validity VFS101. I use it for a couple > of day with good result. > > For verify the implementation i need tester. If i receive positive > feedback i will work to merge it into library. > > Attached the patch for libfprint 0.3.0. To compile it run: > > autoreconf && ./configure && make > > Important: the match score is much variable (on my experience from 10 to > 100) so, to have a good chance to match the fingerprint, it's much > important who scan is done. I use fprint_demo to find the best way to > scan my finger. > > Waiting feedback. > > Bye > Sergio Hi Sergio, I've got a HP dv5 with a VFS101 sensor. Got Your patch tested and it works. I'll use it for a couple of days to test it for stability and let You know later. I'd like to thank You very much for Your work and everyone else who made it possible (Ray). Regards, Suren From pander at users.sourceforge.net Fri Feb 25 15:06:12 2011 From: pander at users.sourceforge.net (Pander) Date: Fri, 25 Feb 2011 16:06:12 +0100 Subject: [fprint] Use fingerprint reader as scroll button Message-ID: <4D67C564.9080204@users.sourceforge.net> Hi all, I have a fingerprint reader such as shown in this image: http://img36.imageshack.us/img36/18/a77b4912d3.jpg In both the following situations: - I use this device for authentication and am authenticated - I am not using this device for authentication but at least the latter situation, I would like to use the fingerprint reader as a scoll wheel. It could be used for: - zooming - vertical scrolling - horizontal scrolling I'm interested especially in using for zooming in and out, which is something like CTRL + SCROLLWHEEL1 in X or GNOME. Would you please consider this as a feature request. Implementing this would provide an extra or alternative scroll wheel in a creative way. Being able to offer zoom or vertical scrolling via this device would allow for more ergonomic use of that functionality without having to use SHIFT or CTRL with the normal scroll wheel. Regards, Pander From pander at users.sourceforge.net Fri Feb 25 15:13:16 2011 From: pander at users.sourceforge.net (Pander) Date: Fri, 25 Feb 2011 16:13:16 +0100 Subject: [fprint] Use fingerprint reader as scroll button In-Reply-To: <4D67C564.9080204@users.sourceforge.net> References: <4D67C564.9080204@users.sourceforge.net> Message-ID: <4D67C70C.8040700@users.sourceforge.net> On 2011-02-25 16:06, Pander wrote: > Hi all, > > I have a fingerprint reader such as shown in this image: > http://img36.imageshack.us/img36/18/a77b4912d3.jpg > > In both the following situations: > - I use this device for authentication and am authenticated > - I am not using this device for authentication > but at least the latter situation, I would like to use the fingerprint > reader as a scoll wheel. > > It could be used for: > - zooming > - vertical scrolling > - horizontal scrolling > > I'm interested especially in using for zooming in and out, which is > something like CTRL + SCROLLWHEEL1 in X or GNOME. Would you please > consider this as a feature request. > > Implementing this would provide an extra or alternative scroll wheel in > a creative way. Being able to offer zoom or vertical scrolling via this > device would allow for more ergonomic use of that functionality without > having to use SHIFT or CTRL with the normal scroll wheel. Apparently I'm not the first to come up with this idea, see: http://lists.reactivated.net/pipermail/fprint/2011-January/001676.html I hope more people will be in favour of this feature. > Regards, > > Pander > _______________________________________________ > fprint mailing list > fprint at reactivated.net > http://lists.reactivated.net/mailman/listinfo/fprint From n.shatokhin at gmail.com Sat Feb 26 16:30:24 2011 From: n.shatokhin at gmail.com (Nicholas Shatokhin) Date: Sat, 26 Feb 2011 18:30:24 +0200 Subject: [fprint] terminate scanning Message-ID: I'm using libfprint in my qt4 project. I'm starting scanning in parallel thread, so it's not freeze program. But how can I terminate scanning? When user closing app, I must finish thread, but I can't do this because scanning freeze the thread. So, how can I abort scanning for destroying thread? -- ?? ???????????? ????????????? ??????? ??????????? ????? Opera: http://www.opera.com/mail/ From anarsoul at gmail.com Sat Feb 26 16:40:46 2011 From: anarsoul at gmail.com (Vasily Khoruzhick) Date: Sat, 26 Feb 2011 18:40:46 +0200 Subject: [fprint] terminate scanning In-Reply-To: References: Message-ID: <201102261840.46782.anarsoul@gmail.com> On Saturday 26 February 2011 18:30:24 Nicholas Shatokhin wrote: > I'm using libfprint in my qt4 project. I'm starting scanning in parallel > thread, so it's not freeze program. But how can I terminate scanning? When > user closing app, I must finish thread, but I can't do this because > scanning freeze the thread. So, how can I abort scanning for destroying > thread? Use asynchronous interface of libfprint, see fprint_demo (not sure if it's still in actual state) for example. Regards Vasily From anarsoul at gmail.com Sat Feb 26 16:57:01 2011 From: anarsoul at gmail.com (Vasily Khoruzhick) Date: Sat, 26 Feb 2011 18:57:01 +0200 Subject: [fprint] terminate scanning In-Reply-To: References: <201102261840.46782.anarsoul@gmail.com> Message-ID: <201102261857.01888.anarsoul@gmail.com> On Saturday 26 February 2011 18:43:20 Nicholas Shatokhin wrote: > Where can I get latest source of fprint_demo? Does it have API reference > manual? https://github.com/dsd/fprint_demo/tree It's an application that uses libfprint async API, so it does not provide any public API. Regards Vasily P.S. Don't remove fprint ML from CC. From ashu210890 at gmail.com Sun Feb 27 04:20:09 2011 From: ashu210890 at gmail.com (Ashu Pachauri) Date: Sun, 27 Feb 2011 09:50:09 +0530 Subject: [fprint] Help: Authentec AES 2501 not working Message-ID: I have libfprint installed on my Fedora 14 i686 system, with Authentec AES 2501 fingerprint reader. The reader worked fine on Fedora 12 some time ago. But, it mysteriously stopped working. Then, I reinstalled Fedora 12, tried on Fedora 13, Fedora 14, and Ubuntu 10.04, but with no luck. However, it still works fine on Windows 7 having Authentec TrueSuite software installed. The problem is: lsusb and usb-devces recgnize the fingerprint reader. #lsusb Bus 007 Device 002: ID 03f0:171d Hewlett-Packard Wireless (Bluetooth + WLAN) Interface [Integrated Module] Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 002: ID 1267:0210 Logic3 / SpectraVideo plc Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 002: ID 08ff:2580 AuthenTec, Inc. AES2501 Fingerprint Sensor Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 04f2:b016 Chicony Electronics Co., Ltd VGA 30fps UVC Webcam Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub #usb-devices ... ... T: Bus=04 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 D: Ver= 1.10 Cls=ff(vend.) Sub=ff Prot=ff MxPS= 8 #Cfgs= 1 P: Vendor=08ff ProdID=2580 Rev=06.23 S: Product=Fingerprint Sensor C: #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) <--- Driver=none ?? I have libfprint installed. ... But, fprintd-enroll simply does nothing while I try to enroll. It gets stuck and nothing happens when I scan my finger. #fprintd-enroll Using device /net/reactivated/Fprint/Device/0 Enrolling right index finger. ^C Please help. -- Ashu Pachauri ZHCET, Aligarh Muslim University -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.reactivated.net/pipermail/fprint/attachments/20110227/5ab99687/attachment.html From poehn at online.de Sun Feb 27 10:05:18 2011 From: poehn at online.de (Sebastian =?ISO-8859-1?B?UPZobg==?=) Date: Sun, 27 Feb 2011 11:05:18 +0100 Subject: [fprint] New driver for Validity VFS101: tester wanted Message-ID: <20110227110518.3e9a117d@Vostro> I got the VFS101 patch, but have a VFS300 (138a:0008). I added its usb-id in vfs101.c , but the device is not detected at all! Is there an other place where I need to add it? Of course I know that the protocol may be very different and the device may not work. From nikodemus at sb-studio.net Sun Feb 27 10:18:49 2011 From: nikodemus at sb-studio.net (Nikodemus Siivola) Date: Sun, 27 Feb 2011 12:18:49 +0200 Subject: [fprint] [PATCH] Allow max_tries in case of failed identification as well Message-ID: <1298801929-12812-1-git-send-email-nikodemus@sb-studio.net> Swipe-type scanners make it hard to get a reliably good scan on the first try, so allow a number of retries before returning with a failure. --- src/pam_fprint.c | 9 +++++++-- 1 files changed, 7 insertions(+), 2 deletions(-) diff --git a/src/pam_fprint.c b/src/pam_fprint.c index 24fc104..b0f6eeb 100644 --- a/src/pam_fprint.c +++ b/src/pam_fprint.c @@ -163,7 +163,8 @@ static int do_identify(pam_handle_t *pamh, struct fp_dev *dev, if (fp_dev_supports_identification(dev)) { - snprintf(msg, sizeof(msg), "Scan finger on %s", driver_name); + snprintf(msg, sizeof(msg), "Scan finger on %s, %d %s left", + driver_name, max_tries, max_tries==1 ? "attempt" : "attempts"); msg[sizeof(msg) - 1] = 0; send_info_msg(pamh, msg); r = fp_identify_finger(dev, gallery, &offset); @@ -183,7 +184,11 @@ static int do_identify(pam_handle_t *pamh, struct fp_dev *dev, } switch (r) { case FP_VERIFY_NO_MATCH: - return PAM_AUTH_ERR; + if (max_tries==1) + return PAM_AUTH_ERR; + else { + break; + } case FP_VERIFY_MATCH: return PAM_SUCCESS; case FP_VERIFY_RETRY: -- 1.7.1 From kunal.gangakhedkar at gmail.com Sun Feb 27 10:56:57 2011 From: kunal.gangakhedkar at gmail.com (Kunal Gangakhedkar) Date: Sun, 27 Feb 2011 16:26:57 +0530 Subject: [fprint] New driver for Validity VFS101: tester wanted In-Reply-To: <20110227110518.3e9a117d@Vostro> References: <20110227110518.3e9a117d@Vostro> Message-ID: <201102271626.57570.kunal.gangakhedkar@gmail.com> On Sunday 27 Feb 2011 3:35:18 pm Sebastian P?hn wrote: > I got the VFS101 patch, but have a VFS300 (138a:0008). I added its > usb-id in vfs101.c , but the device is not detected at all! Is there an > other place where I need to add it? > What's the error? If you get a 'Permission Denied' message, that means you need to run the enroll/verify examples as root/sudo. You may want to compile the library with '--enable-debug-log' option to configure. This enables dumping of debug messages onto stderr. Kunal > Of course I know that the protocol may be very different and the device > may not work. > _______________________________________________ > fprint mailing list > fprint at reactivated.net > http://lists.reactivated.net/mailman/listinfo/fprint > From kunal.gangakhedkar at gmail.com Sun Feb 27 10:50:56 2011 From: kunal.gangakhedkar at gmail.com (Kunal Gangakhedkar) Date: Sun, 27 Feb 2011 16:20:56 +0530 Subject: [fprint] New driver for Validity VFS101: tester wanted In-Reply-To: <1298623763.494.16.camel@cerlyLp> References: <1298623763.494.16.camel@cerlyLp> Message-ID: <201102271620.57019.kunal.gangakhedkar@gmail.com> Hi Sergio, Awesome work !! Got the patch working on my HP dv6 notebook having the VFS101 sensor. Two issues: o. on my sensor, the img_screen() function was always returning image height = 1. I added a fp_dbg() call to dump the values in the loop variables to figure out what was going on. The 'break' statement in the 'find bottom of image' part is not correct since it aborts the screening prematurely. Due to this break, the screened image height always ended up = 1 in my case. This happens even during the enrollment phase. I have the logs dumped - let me know if you want to take a look at them. o. during verification, if I end up just touching the sensor and lifting the finger, I get a message 'Unexpected finger find, remove finger from sensor'. But, it goes into an infinite loop with the same msg since the device's bufffer still contains the old image data. The device buffer needs to be flushed upon any such error conditions. I'm attaching a patch on top of your code that tries to fix both the problems. Please let me know if it looks OK. Thanks, Kunal On Friday 25 Feb 2011 2:19:23 pm Sergio Cerlesi wrote: > Hi all, > > i finish to write the driver fo Validity VFS101. I use it for a couple > of day with good result. > > For verify the implementation i need tester. If i receive positive > feedback i will work to merge it into library. > > Attached the patch for libfprint 0.3.0. To compile it run: > > autoreconf && ./configure && make > > Important: the match score is much variable (on my experience from 10 to > 100) so, to have a good chance to match the fingerprint, it's much > important who scan is done. I use fprint_demo to find the best way to > scan my finger. > > Waiting feedback. > > Bye > Sergio > -------------- next part -------------- A non-text attachment was scrubbed... Name: vfs101-fixes.diff Type: text/x-patch Size: 2173 bytes Desc: not available Url : http://lists.reactivated.net/pipermail/fprint/attachments/20110227/d28044b5/vfs101-fixes.bin From hadess at hadess.net Sun Feb 27 17:31:54 2011 From: hadess at hadess.net (Bastien Nocera) Date: Sun, 27 Feb 2011 17:31:54 +0000 Subject: [fprint] [PATCH] Allow max_tries in case of failed identification as well In-Reply-To: <1298801929-12812-1-git-send-email-nikodemus@sb-studio.net> References: <1298801929-12812-1-git-send-email-nikodemus@sb-studio.net> Message-ID: <1298827915.9131.0.camel@novo.hadess.net> On Sun, 2011-02-27 at 12:18 +0200, Nikodemus Siivola wrote: > Swipe-type scanners make it hard to get a reliably good scan on the > first try, so allow a number of retries before returning with a > failure. > --- > src/pam_fprint.c | 9 +++++++-- pam_fprint is deprecated, please make those changes (if necessary) against pam_fprintd, part of the fprintd package. Cheers From hadess at hadess.net Sun Feb 27 18:08:54 2011 From: hadess at hadess.net (Bastien Nocera) Date: Sun, 27 Feb 2011 18:08:54 +0000 Subject: [fprint] Help: Authentec AES 2501 not working In-Reply-To: References: Message-ID: <1298830135.9131.4.camel@novo.hadess.net> On Sun, 2011-02-27 at 09:50 +0530, Ashu Pachauri wrote: > I have libfprint installed on my Fedora 14 i686 system, with Authentec > AES 2501 fingerprint reader. The reader worked fine on Fedora 12 some > time ago. But, it mysteriously stopped working. Then, I reinstalled > Fedora 12, tried on Fedora 13, Fedora 14, and Ubuntu 10.04, but with > no luck. However, it still works fine on Windows 7 having Authentec > TrueSuite software installed. It should work. > I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) > <--- Driver=none ?? I have > libfprint installed. libfprint isn't a kernel driver. > But, fprintd-enroll simply does nothing while I try to enroll. It gets > stuck and nothing happens when I scan my finger. > > > #fprintd-enroll > Using device /net/reactivated/Fprint/Device/0 > Enrolling right index finger. > ^C Try disabling autosuspend for this driver, by editing out the line for your device in /etc/udev/rules.d/60-fprint-autosuspend.rules and reboot your computer (if the device is builtin), or unplug/replug if it's external. Let me know if it work better afterwards. Cheers From hadess at hadess.net Sun Feb 27 19:30:24 2011 From: hadess at hadess.net (Bastien Nocera) Date: Sun, 27 Feb 2011 19:30:24 +0000 Subject: [fprint] terminate scanning In-Reply-To: References: Message-ID: <1298835026.9131.10.camel@novo.hadess.net> On Sat, 2011-02-26 at 18:30 +0200, Nicholas Shatokhin wrote: > I'm using libfprint in my qt4 project. I'm starting scanning in parallel > thread, so it's not freeze program. But how can I terminate scanning? When > user closing app, I must finish thread, but I can't do this because > scanning freeze the thread. So, how can I abort scanning for destroying > thread? As mentioned before, you should use fprintd, which provides D-Bus bindings just for that purpose. Furthermore, it wouldn't require user access to the fingerprint reader, and would hide all the reading of enrolled fingerprints from the user-space application. From n.shatokhin at gmail.com Sun Feb 27 21:18:42 2011 From: n.shatokhin at gmail.com (Nicholas Shatokhin) Date: Sun, 27 Feb 2011 23:18:42 +0200 Subject: [fprint] libfprint async api Message-ID: Hello, I found that async api has not have any documentation yet. But biggest part of programs use GUI and need it. Maybe it's a good idea to create this (even just a list of functions). Best regards, Nick. -- ?? ???????????? ????????????? ??????? ??????????? ????? Opera: http://www.opera.com/mail/ From n.shatokhin at gmail.com Sun Feb 27 23:43:26 2011 From: n.shatokhin at gmail.com (Nicholas Shatokhin) Date: Mon, 28 Feb 2011 01:43:26 +0200 Subject: [fprint] Licensing Message-ID: Hello. Can I use libfprint in my commercial proprietary project? How can I do it? Best regards, Nick. -- ?? ???????????? ????????????? ??????? ??????????? ????? Opera: http://www.opera.com/mail/ From hadess at hadess.net Mon Feb 28 09:08:42 2011 From: hadess at hadess.net (Bastien Nocera) Date: Mon, 28 Feb 2011 09:08:42 +0000 Subject: [fprint] Licensing In-Reply-To: References: Message-ID: <1298884123.3024.0.camel@novo.hadess.net> On Mon, 2011-02-28 at 01:43 +0200, Nicholas Shatokhin wrote: > Hello. > > Can I use libfprint in my commercial proprietary project? How can I do it? The project is licensed under the LGPL v2.1. See the COPYING file for details, and contact a lawyer if you want to find out if it's suitable >From my point of view, it would be fine to do so, as long as you submit your changes to libfprint back to us. Cheers From sergio.cerlesi at gmail.com Mon Feb 28 10:07:44 2011 From: sergio.cerlesi at gmail.com (Sergio Cerlesi) Date: Mon, 28 Feb 2011 11:07:44 +0100 Subject: [fprint] New driver for Validity VFS101: tester wanted In-Reply-To: <201102271620.57019.kunal.gangakhedkar@gmail.com> References: <1298623763.494.16.camel@cerlyLp> <201102271620.57019.kunal.gangakhedkar@gmail.com> Message-ID: <1298887664.18927.4.camel@cerlyLp> Hi Kunal, thank for feedback and patch. I will investigate on the two issues, could you send me the log ? The issues you report are occasional or systematic ? Bye Sergio Il giorno dom, 27/02/2011 alle 16.20 +0530, Kunal Gangakhedkar ha scritto: > Hi Sergio, > > Awesome work !! > Got the patch working on my HP dv6 notebook having the VFS101 sensor. > > Two issues: > o. on my sensor, the img_screen() function was always returning > image height = 1. I added a fp_dbg() call to dump the values > in the loop variables to figure out what was going on. > The 'break' statement in the 'find bottom of image' part > is not correct since it aborts the screening prematurely. > Due to this break, the screened image height always ended up = 1 > in my case. > > This happens even during the enrollment phase. > I have the logs dumped - let me know if you want to take a look at them. > > o. during verification, if I end up just touching the sensor and lifting the > finger, I get a message 'Unexpected finger find, remove finger from sensor'. > But, it goes into an infinite loop with the same msg since the device's > bufffer still contains the old image data. The device buffer needs to be > flushed upon any such error conditions. > > I'm attaching a patch on top of your code that tries to fix both the problems. > Please let me know if it looks OK. > > Thanks, > Kunal > > On Friday 25 Feb 2011 2:19:23 pm Sergio Cerlesi wrote: > > Hi all, > > > > i finish to write the driver fo Validity VFS101. I use it for a couple > > of day with good result. > > > > For verify the implementation i need tester. If i receive positive > > feedback i will work to merge it into library. > > > > Attached the patch for libfprint 0.3.0. To compile it run: > > > > autoreconf && ./configure && make > > > > Important: the match score is much variable (on my experience from 10 to > > 100) so, to have a good chance to match the fingerprint, it's much > > important who scan is done. I use fprint_demo to find the best way to > > scan my finger. > > > > Waiting feedback. > > > > Bye > > Sergio > > > From ashu210890 at gmail.com Mon Feb 28 15:00:02 2011 From: ashu210890 at gmail.com (Ashu Pachauri) Date: Mon, 28 Feb 2011 20:30:02 +0530 Subject: [fprint] Help: Authentec AES 2501 not working In-Reply-To: <1298830135.9131.4.camel@novo.hadess.net> References: <1298830135.9131.4.camel@novo.hadess.net> Message-ID: Thanks for your reply. Try disabling autosuspend for this driver, by editing out the line for > your device in /etc/udev/rules.d/60-fprint-autosuspend.rules > and reboot your computer (if the device is builtin), or unplug/replug if > it's external. > I disabled autosuspend by editing the line for my device and setting power/level to "on" instead of "auto". But, the problem persists. I also tried using usbcore.autosuspend=-1 as a kernel argument, but no luck. I mean I have tried nearly everything on my end, what more can I do? -- Ashu Pachauri ZHCET, Aligarh Muslim University -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.reactivated.net/pipermail/fprint/attachments/20110228/f6bd4d8e/attachment.html