[fprint] When you mean unencrypted image..

[sergio cerlesi]

Hi Javier,

the patch is write for libfprint 0.3.0. With this version of libfprint you
can apply the patch without error:

libfprint-0.3.0 $ patch -p1 < ../vfs101-driver.patch
patching file libfprint/drivers/vfs101.c
patching file libfprint/fp_internal.h
patching file libfprint/core.c
patching file libfprint/Makefile.am
patching file configure.ac
libfprint-0.3.0 $ patch -p1 < ../vfs101-driver-compile-fix.patch
patching file libfprint/drivers/vfs101.c

You can download the library at this link:

http://people.freedesktop.org/~hadess/libfprint-0.3.0.tar.bz2

Before compile it you need to run autoreconf (or autoconf && autoheader &&
automake if you prefere) and ./configure.

If you have a compile error due to dump_buffer define you can apply the
attached patch (yesterday i not remember to send it).

Bye
Sergio

2011/1/21 Javier Domingo <javierdo1 at gmail.com>

> I have had problems with the patch (you should update it), I fixed it
> manually. For example the Makefile is not as it figures in the patch. "I
> think I patched" files correctly... so we'll see... for the moment I am
> going to suicide... I have to install dependecies:
>
>    - glib
>    - imagemagic
>    - libusb
>    - libssl-dev
>
>
>
> (I think this should also be installed automaticly in the official
> version...)
>
> Edit: I am updating your patch to fix the new version... I have a strange
> problem, it interprets as if all the files of the patch would be in the same
> directory... but except for that, It is starting to work... I have stuct
> because It tells me this:
>
> make  all-recursive
>
> make[1]: se ingresa al directorio «/home/javier/pruebas/libi»
>
> Making all in libfprint
>
> make[2]: se ingresa al directorio «/home/javier/pruebas/libi/libfprint»
>
> /bin/bash ../libtool --tag=CC   --mode=link gcc -fvisibility=hidden
>> -I./nbis/include -I/usr/local/include/libusb-1.0
>> -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include   -fopenmp
>> -I/usr/local/include/ImageMagick    -std=gnu99 -fgnu89-inline -Wall -Wundef
>> -Wunused -Wstrict-prototypes -Werror-implicit-function-declaration
>> -Wno-pointer-sign -Wshadow -g -O2   -o fprint-list-hal-info
>> fprint_list_hal_info-fprint-list-hal-info.o ./libfprint.la
>
>  libtool: link: gcc -fvisibility=hidden -I./nbis/include
>> -I/usr/local/include/libusb-1.0 -I/usr/local/include/glib-2.0
>> -I/usr/local/lib/glib-2.0/include -fopenmp -I/usr/local/include/ImageMagick
>> -std=gnu99 -fgnu89-inline -Wall -Wundef -Wunused -Wstrict-prototypes
>> -Werror-implicit-function-declaration -Wno-pointer-sign -Wshadow -g -O2 -o
>> .libs/fprint-list-hal-info fprint_list_hal_info-fprint-list-hal-info.o
>>  ./.libs/libfprint.so -pthread
>
>  ./.libs/libfprint.so: undefined reference to `vfs101_driver'
>
> collect2: ld returned 1 exit status
>
> make[2]: *** [fprint-list-hal-info] Error 1
>
> make[2]: se sale del directorio «/home/javier/pruebas/libi/libfprint»
>
> make[1]: *** [all-recursive] Error 1
>
> make[1]: se sale del directorio «/home/javier/pruebas/libi»
>
> make: *** [all] Error 2
>
>
> I ll work on this tomorrow (later today ;) (3am here) ) and when I fix it,
> I will send u the patch
>
> Best Regards,
>
>
>
> 2011/1/20 sergio cerlesi <sergio.cerlesi at gmail.com>
>
>> When you test the driver on your system, can you send me a feedback ?
>>
>> For the driver, if you have any questions i'm here.
>>
>> Bye
>>
>> Sergio
>>
>> 2011/1/20 Javier Domingo <javierdo1 at gmail.com>
>>
>>> Puf,
>>> ¡I thought no one was working on it!, I will start to study your driver,
>>> and then I will try to help. I have a hp probook, so I can also test it. I
>>> will spend some days researching on this,
>>>
>>> Thank you!
>>>
>>> 2011/1/20 sergio cerlesi <sergio.cerlesi at gmail.com>
>>>
>>> Hi,
>>>>
>>>> if you are interesting you can find more information at this link:
>>>>
>>>> https://github.com/rayl/vfs101driver
>>>>
>>>> On free time (not more realy) i'm working on fprint driver (attached
>>>> patch). It's base on Rayl work. On my system it seem stable but i need to
>>>> work on clean up the raw image.
>>>>
>>>> Help is welcome.
>>>>
>>>> By
>>>> Sergio
>>>>
>>>>
>>>> 2011/1/20 Javier Domingo <javierdo1 at gmail.com>
>>>>
>>>>>  Hello,
>>>>>
>>>>> I have been doing packet sniffs of the VFS101, you did a previous
>>>>> analisys of them, and you said "image is unencrypted"<http://reactivated.net/fprint/wiki/Unsupported_devices#Validity_VFS101>,
>>>>> how should I interpret that image? png, bmp? what do you use to take those
>>>>> images?
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Javier Domingo
>>>>>
>>>>> _______________________________________________
>>>>> fprint mailing list
>>>>> fprint at reactivated.net
>>>>> http://lists.reactivated.net/mailman/listinfo/fprint
>>>>>
>>>>>
>>>>
>>>
>>>
>>> --
>>> Javier Domingo
>>>
>>
>>
>
>
> --
> Javier Domingo
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.reactivated.net/pipermail/fprint/attachments/20110121/fff152db/attachment-0001.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: vfs101-driver-compile-fix.patch
Type: application/octet-stream
Size: 491 bytes
Desc: not available
Url : http://lists.reactivated.net/pipermail/fprint/attachments/20110121/fff152db/vfs101-driver-compile-fix-0001.obj