http://blog.gmane.org/gmane.linux.fprint hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.linux.fprint/2300 <pre>ok if you comment I used to opensuse but the link to install does not work, could you help me please the link is: http://download.opensuse.org/repositories/home:/dgege/ or you could guide me in the installation with opensuse _______________________________________________ fprint mailing list fprint&lt; at &gt;lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/fprint </pre> Roberto Antonio Herrera 2013-05-14T17:50:24 http://permalink.gmane.org/gmane.linux.fprint/2299 <pre> yes. </pre> Igor Gnatenko 2013-05-13T22:32:24 http://permalink.gmane.org/gmane.linux.fprint/2298 <pre>the fprint can be used on opensuse? since I've been trying to install and I could or distro Lunux that can be used right? _______________________________________________ fprint mailing list fprint&lt; at &gt;lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/fprint </pre> Roberto Antonio Herrera 2013-05-13T22:06:56 http://permalink.gmane.org/gmane.linux.fprint/2297 <pre>Hi Dan, Thanks for confirmation, I thought it was just AES3500 performs badly. Is it the matching approach (i.e. minuates detection and matching in NBIS) that poses a limitation on verification of these kind devices? Is the Windows driver using a completely different approach on verification? Sorry, my experiences are very limited, would very much like to get your advice! Thanks! best, -- jv ♫ m: (+86) 156 5238 4808 On Wed, May 8, 2013 at 10:03 PM, Daniel Drake &lt;dan&lt; at &gt;reactivated.net&gt; wrote: _______________________________________________ fprint mailing list fprint&lt; at &gt;lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/fprint </pre> Juvenn Woo 2013-05-09T01:16:28 http://permalink.gmane.org/gmane.linux.fprint/2296 <pre>El 08/05/13 02:54, Juvenn Woo escribió: The AES4000 driver performs badly as well. As you've commented, the likely problem is that only a tiny area of the finger is sampled. I imagine the windows driver (where the sensor seems to perform OK) has a fingerprint processing engine heavily tuned to small amounts of data. It's probably quite insecure as a result. Thanks for the contribution! Daniel </pre> Daniel Drake 2013-05-08T14:03:21 http://permalink.gmane.org/gmane.linux.fprint/2295 <pre>Dear all, I'm submitting the AES3500 driver for peers to review. The AES3500 is a pretty old fingerprint device produced by AuthenTech. It possesses a *press-typed* sensor of dimension in 128x128. Which is similiar to AES4000, except the later is in 96x96. The driver is a deriative work of Daniel Drake's AES4000 driver, with a few parameters tuned for AES3500. While there seems no problem scanning fingerprint images with it, the verification rate is pretty low at the moment. Your contributions are very welcome. * The bugzilla submission: https://bugs.freedesktop.org/show_bug.cgi?id=64351 * Github repo: https://github.com/juvenn/aes3500 Thanks! best, -- jv _______________________________________________ fprint mailing list fprint&lt; at &gt;lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/fprint </pre> Juvenn Woo 2013-05-08T08:54:30 http://permalink.gmane.org/gmane.linux.fprint/2294 <pre>Sorry, newzenca! I think I'd missed your email. Thank you for offering help. As said in the Paul's thread of "AES3500 test report", I will clean the code a bit, and submit a patch. Will have a look at your diff as well. On Apr 20, 2013 1:22 AM, "newzenca" &lt;newzenca&lt; at &gt;gmail.com&gt; wrote: _______________________________________________ fprint mailing list fprint&lt; at &gt;lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/fprint </pre> Juvenn Woo 2013-05-05T13:58:04 http://permalink.gmane.org/gmane.linux.fprint/2293 <pre>Yes, Paul, it's my pleasure to do so, and thank you for testing and evaluating it. You're right it's a little too small for a press-typed sensor, which could capture only a sub-area of fingerprint, yet the device works pretty good on Windows. So I'm inclined to think there could have rooms for improvements. And, I was not aware of the 90 degree rotation, I think I must have missed some params to tweak. Maybe we could later work it out al-together. I will clean the code a bit against current HEAD of libfprint before I submit the patch, and will share the docs and toolkits I had used along the way. Will let you know then! Hello, I've tested Juvenn's patch as linked in recent message thread on the mailing list: https://gist.github.com/juvenn/939298 . It bitrotted a bit wrt to current HEAD, but was trivial to fix. I should say that I didn't have much first-hand experience with fingerprint scanning devices. Except for random cases which almost everyone experienced, like you go to some office, where they have safe with fingerprint lock, which they can't open for half an hour and then call a technician with a hammer to work around the technology. Neither I tried to look up that NIST "NBIS" thingy. But when I was a young student I registered for access to a handwriting recognition system from them, which arrived in snail mail on a CD with a nice printed manual which said that the system achieves recognition rate of 36.578% and its sole purpose is to serve as a baseline for evaluating other handwriting recognition systems. So, my wild guess is that NBIS is just the same. So, I'm not at all surprised with the initial results I got, which match those posted by another subscriber: I had troubles enrolling a finger, and then recognizing, while fingerprint images shown by fprint_demo were pretty legible. Some thinking helped though. First of all, AES3500 cannot capture a *fingerprint*, it just physically too small for that. It can capture only small sub-area of it, then depending on how exactly you put your finger on it, areas will be rather different, likely straining NBIS. As a fingerprinting layman, I also put my index finger's tip on the sensor, and the tip contains almost parallel lines, and probably lacks enough features to recognize. Shape of my APC Biopod kinda suggests that they aim for thumb's fingerpad instead, which has curves and stuff. All in all, the best results I expectedly had with small finger - the sensor can capture pretty large part of it. Except that NBIS couldn't tell the difference between my left and right little fingers. All in all, specifically AES3500 image capture driver works pretty well - fingerprint lines are black, spaces between them are white, grayscale shades are there. The only thing I noticed is that scanned image is apparently rotated 90 degrees (i.e. mostly horizontal fingerprint lines are shown vertically), not sure if that presents additional puzzle for NBIS. So, +1 for merging the patch, Juvenn, would you submit it via fprint bugtracker, as was suggested by Vasily? Thanks, Paul mailto:pmiscml&lt; at &gt;gmail.com _______________________________________________ fprint mailing list fprint&lt; at &gt;lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/fprint </pre> Juvenn Woo 2013-05-05T02:21:48 http://permalink.gmane.org/gmane.linux.fprint/2292 <pre>Hello, On Sat, 04 May 2013 17:27:12 +0100 Tom Chiverton &lt;tom+fprint&lt; at &gt;falkensweb.com&gt; wrote: Yeah, I'd think that's definitely how "narrow slot" type fingerprint readers work - you swipe a finger across the sensor. But there're also those which has large enough area where you just press finger against. AES3500 would look like this second type (photo of my device: http://www.strobey.co.uk/pics/aes3400/biopod.jpg) - except that well, sensor area 6.5x6.5mm is a bit too small to capture big enough part of entire fingerprint, which leads to a repeatable finger positioning problems. I tried to swipe a finger against it too, but nope, fprint_demo captures just square image on first contact. </pre> Paul Sokolovsky 2013-05-04T20:13:23 http://permalink.gmane.org/gmane.linux.fprint/2291 <pre> I've not even wikipedia'ed it, admittedly, but rather thought fprint was stitching together a series of snap shots taken as you move your finger down across the face of the camera. Much like a panorama feature in many cameras... </pre> Tom Chiverton 2013-05-04T16:27:12 http://permalink.gmane.org/gmane.linux.fprint/2290 <pre>Hello, I've tested Juvenn's patch as linked in recent message thread on the mailing list: https://gist.github.com/juvenn/939298 . It bitrotted a bit wrt to current HEAD, but was trivial to fix. I should say that I didn't have much first-hand experience with fingerprint scanning devices. Except for random cases which almost everyone experienced, like you go to some office, where they have safe with fingerprint lock, which they can't open for half an hour and then call a technician with a hammer to work around the technology. Neither I tried to look up that NIST "NBIS" thingy. But when I was a young student I registered for access to a handwriting recognition system from them, which arrived in snail mail on a CD with a nice printed manual which said that the system achieves recognition rate of 36.578% and its sole purpose is to serve as a baseline for evaluating other handwriting recognition systems. So, my wild guess is that NBIS is just the same. So, I'm not at all surprised with the initial results I got, which match those posted by another subscriber: I had troubles enrolling a finger, and then recognizing, while fingerprint images shown by fprint_demo were pretty legible. Some thinking helped though. First of all, AES3500 cannot capture a *fingerprint*, it just physically too small for that. It can capture only small sub-area of it, then depending on how exactly you put your finger on it, areas will be rather different, likely straining NBIS. As a fingerprinting layman, I also put my index finger's tip on the sensor, and the tip contains almost parallel lines, and probably lacks enough features to recognize. Shape of my APC Biopod kinda suggests that they aim for thumb's fingerpad instead, which has curves and stuff. All in all, the best results I expectedly had with small finger - the sensor can capture pretty large part of it. Except that NBIS couldn't tell the difference between my left and right little fingers. All in all, specifically AES3500 image capture driver works pretty well - fingerprint lines are black, spaces between them are white, grayscale shades are there. The only thing I noticed is that scanned image is apparently rotated 90 degrees (i.e. mostly horizontal fingerprint lines are shown vertically), not sure if that presents additional puzzle for NBIS. So, +1 for merging the patch, Juvenn, would you submit it via fprint bugtracker, as was suggested by Vasily? Thanks, Paul mailto:pmiscml&lt; at &gt;gmail.com </pre> Paul Sokolovsky 2013-05-04T15:15:29 http://permalink.gmane.org/gmane.linux.fprint/2289 <pre>Hi Paul, see https://bugs.freedesktop.org/show_bug.cgi?id=60445 Regards Vasily On Sat, May 4, 2013 at 5:12 PM, Paul Sokolovsky &lt;pmiscml&lt; at &gt;gmail.com&gt; wrote: _______________________________________________ fprint mailing list fprint&lt; at &gt;lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/fprint </pre> Vasily Khoruzhick 2013-05-04T15:13:09 http://permalink.gmane.org/gmane.linux.fprint/2288 <pre>Hello, I'd like to to help with testing recently posted AES3500 patch. Running img_capture example (output filtered): -------- $ sudo ./examples/img_capture supports USB device 08ff:5731 Found device claimed by AuthenTec AES3500 Opened device. It's now time to scan your finger. image capture failed, code -95 sync:debug [fp_dev_close] -------- $ git blame core.c -------- 7e6f2590 (Daniel Drake 2007-11-02 17:04:19 +0000 840) API_EXPORTED int fp_dev_img_capture(struct fp_dev *dev, int unconditional, 7e6f2590 (Daniel Drake 2007-11-02 17:04:19 +0000 841) struct fp_img **image) 7e6f2590 (Daniel Drake 2007-11-02 17:04:19 +0000 842) { 7e6f2590 (Daniel Drake 2007-11-02 17:04:19 +0000 843) struct fp_img_dev *imgdev = dev_to_img_dev(dev); 7e6f2590 (Daniel Drake 2007-11-02 17:04:19 +0000 844) if (!imgdev) { 7e6f2590 (Daniel Drake 2007-11-02 17:04:19 +0000 845) fp_dbg("image capture on non-imaging device"); 7e6f2590 (Daniel Drake 2007-11-02 17:04:19 +0000 846) return -ENOTSUP; 7e6f2590 (Daniel Drake 2007-11-02 17:04:19 +0000 847) } 7e6f2590 (Daniel Drake 2007-11-02 17:04:19 +0000 848) 3048b371 (Daniel Drake 2008-02-10 18:35:01 +0000 849) //return fpi_imgdev_capture(imgdev, unconditional, image); 3048b371 (Daniel Drake 2008-02-10 18:35:01 +0000 850) /* FIXME reimplement async */ 3048b371 (Daniel Drake 2008-02-10 18:35:01 +0000 851) return -ENOTSUP; I.e. 2008, fp_dev_img_capture() was made unconditionally return -ENOTSUP. fpi_imgdev_capture() is declared in fp_internal.h but implementation not available. Thus, basic libfprint tests - capturing fingerprint images - appear to be broken for 5 years. Am I missing something? Thanks, Paul mailto:pmiscml&lt; at &gt;gmail.com </pre> Paul Sokolovsky 2013-05-04T14:12:37 http://permalink.gmane.org/gmane.linux.fprint/2287 <pre> Hi David, Thanks! OK, but I've no vfs101 device to test. OK OK I don't want to touch nbis code until it fails _______________________________________________ fprint mailing list fprint&lt; at &gt;lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/fprint </pre> Vasily Khoruzhick 2013-04-30T08:55:21 http://permalink.gmane.org/gmane.linux.fprint/2286 <pre>Hello there, I just ran the static analyser "cppcheck" over the source code of libfprint-0.5.0 and it said 1. [drivers/vfs101.c:192]: (warning) Logical conjunction always evaluates to false: result &lt; 0 &amp;&amp; result &gt;= 3. Suggest replace &amp;&amp; with || 2. [img.c:154]: (error) Resource leak: fd [drivers/aesx660.c:296]: (error) Memory leak: stripdata [nbis/bozorth3/bz_alloc.c:116]: (error) Memory leak: p [nbis/bozorth3/bz_io.c:421]: (error) Resource leak: fp [nbis/mindtct/init.c:593]: (error) Memory leak: powers [nbis/mindtct/init.c:682]: (error) Memory leak: powmax_dirs [nbis/mindtct/maps.c:662]: (error) Memory leak: cimage [nbis/mindtct/maps.c:722]: (error) Memory leak: pmap [nbis/mindtct/maps.c:729]: (error) Memory leak: pmap I checked the first couple and they did look like real problems, although minor. Regards David Binderman </pre> David Binderman 2013-04-30T08:02:08 http://permalink.gmane.org/gmane.linux.fprint/2285 <pre>Hi, When trying to compile with the library Libfprint. I get the following errors. /home/pablo/futronic/verify/fprint.h:237: undefined reference to `fp_identify_finger_img' /home/pablo/futronic/verify/verify.c:65: undefined reference to `fp_dscv_dev_for_dscv_print' /home/pablo/futronic/verify/verify.c:66: undefined reference to `fp_dscv_print_get_driver_id' /home/pablo/futronic/verify/verify.c:71: undefined reference to `fp_dscv_print_get_driver_id' /home/pablo/futronic/verify/verify.c:95: undefined reference to `fp_dscv_print_get_driver_id' /home/pablo/futronic/verify/verify.c:97: undefined reference to `fp_print_data_from_dscv_print' /home/pablo/futronic/verify/verify.c:102: undefined reference to `fp_dscv_print_get_finger' /home/pablo/futronic/verify/verify.c:169: undefined reference to `fp_init' /home/pablo/futronic/verify/verify.c:175: undefined reference to `fp_discover_devs' /home/pablo/futronic/verify/verify.c:181: undefined reference to `fp_discover_prints' /home/pablo/futronic/verify/verify.c:183: undefined reference to `fp_dscv_devs_free' /home/pablo/futronic/verify/verify.c:190: undefined reference to `fp_dscv_prints_free' /home/pablo/futronic/verify/verify.c:191: undefined reference to `fp_dscv_devs_free' /home/pablo/futronic/verify/verify.c:197: undefined reference to `fp_dev_open' /home/pablo/futronic/verify/verify.c:198: undefined reference to `fp_dscv_devs_free' /home/pablo/futronic/verify/verify.c:199: undefined reference to `fp_dscv_prints_free' /home/pablo/futronic/verify/verify.c:203: undefined reference to `fp_print_data_free' /home/pablo/futronic/verify/verify.c:218: undefined reference to `fp_print_data_free' /home/pablo/futronic/verify/verify.c:223: undefined reference to `fp_dev_close' Try installing "" libfprint "package in Ubuntu" solve the problem? Of course, I appreciate any suggestion. Pablo. _______________________________________________ fprint mailing list fprint&lt; at &gt;lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/fprint </pre> Pablo Ignacio Calvo 2013-04-29T18:19:32 http://permalink.gmane.org/gmane.linux.fprint/2284 <pre>Thanks for the tip. It did solve it :). On Sat, Apr 27, 2013 at 10:23 PM, Tom Chiverton &lt;tom+fprint&lt; at &gt;falkensweb.com&gt;wrote: _______________________________________________ fprint mailing list fprint&lt; at &gt;lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/fprint </pre> Oz Tamari 2013-04-28T11:58:12 http://permalink.gmane.org/gmane.linux.fprint/2283 <pre> That was me :-) All I can say is I made sure to enrol as large (covering the whole top to bottom) of my finger(s) as I could. This made verifying mcuh more reliable; about 70% of the time it'll get it on the first swipe. </pre> Tom Chiverton 2013-04-27T19:23:34 http://permalink.gmane.org/gmane.linux.fprint/2282 <pre>Hi, I have the same problem the is described in this thread&lt;http://www.mail-archive.com/fprint&lt; at &gt;lists.freedesktop.org/msg00280.html&gt; . My setup is: Gentoo, libfprint-0.5.0, fprintd-0.4.1 ozt&lt; at &gt;plan9 ~ $ fprintd-enroll -f 7 Using device /net/reactivated/Fprint/Device/0 Enrolling right index finger. Enroll result: enroll-completed ozt&lt; at &gt;plan9 ~ $ fprintd-verify -f 7 Using device /net/reactivated/Fprint/Device/0 Listing enrolled fingers: - #0: right-index-finger Verify result: verify-no-match (done) ozt&lt; at &gt;plan9 ~ $ lsusb Bus 004 Device 002: ID 08ff:2810 AuthenTec, Inc. AES2810 /var/log/messages Apr 26 14:08:34 localhost dbus[2036]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper) Apr 26 14:08:34 localhost dbus[2036]: [system] Successfully activated service 'net.reactivated.Fprint' I tried this numerous times with various fingers and it always give me the same results. I think fingerprint scans are in good quality by examining the scan photo from 'fprint_demo'. I compiled 'libfprint' with debug and collected 'fprint_demo' debug (attached). thanks and let me know if anything else is missing. Regards, Oz _______________________________________________ fprint mailing list fprint&lt; at &gt;lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/fprint </pre> Oz Tamari 2013-04-26T19:43:30 http://permalink.gmane.org/gmane.linux.fprint/2281 <pre> It's very good as far as I can tell, attached. Tom_______________________________________________ fprint mailing list fprint&lt; at &gt;lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/fprint </pre> Tom Chiverton 2013-04-19T17:23:57 http://permalink.gmane.org/gmane.linux.fprint/2280 <pre>https://gist.github.com/juvenn/939298 I downloaded the diff file. In the actual version of libfprint not exactly correspond, make some changes based in the actual version of aes4000 driver. The result new aes3500.dif is attached in git form. There is some more changes because im running centos 6 and Not have glib greater than 2.28 which are taked from this mail http://lists.freedesktop.org/archives/fprint/2013-January/000414.html basically /*g_slist_free_full(aesdev-&gt;strips, g_free);*/ g_slist_foreach(aesdev-&gt;strips, (GFunc) g_free, NULL); g_slist_free(aesdev-&gt;strips); and in configure.ac -PKG_CHECK_MODULES(GLIB, [glib-2.0 &gt;= 2.28]) +PKG_CHECK_MODULES(GLIB, [glib-2.0 &gt;= 2.00]) The unit APC BIOPOD is now capturing images but have a lot of problem for verify my own fingerprint, fail 9 of 10 times. its related to images or driver? El vie, 19-04-2013 a las 21:26 +0300, Vasily Khoruzhick escribió: _______________________________________________ fprint mailing list fprint&lt; at &gt;lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/fprint </pre> newzenca 2013-04-19T23:12:26 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.linux.fprint