On the road to libfprint v2.0, here's 1.90.1:
- Add support for prints saved on the fingerprint device itself
- Add integration tests using the virtual image driver, and further
tests for the utilities
- Port build system to meson
- Loads of build warnings and memory leak fixes
- PAM module:
Hello Dave,
On Mon, 2019-08-19 at 12:04 +0800, Dave.Wang wrote:
> Dear,
>
> As I knew, the daemon program named fprintd can not get the image
> data and
> the corresponding debug messages while enrolling and verifying, only
> the
> tools in libfprint/examples can get the debug image.
That's on p
Hey,
I've just released libfprint 1.0:
https://gitlab.freedesktop.org/libfprint/libfprint/-/releases
It contains a lot of bug fixes for a number of different drivers, which
would make it better for any stable or unstable release of your OS.
Note that there was a small ABI break between versions
On Wed, 2019-07-10 at 14:09 +0200, Benjamin Berg wrote:
> Hi everyone,
>
> so, I have worked on this for a while now, and I pushed my changes to
> the
>
> https://gitlab.freedesktop.org/libfprint/libfprint/commits/wip/benzea/v2
> branch.
>
> This is not yet quite complete. Some changes are mor
On Thu, 2019-06-13 at 16:37 +, Danil Gorelik wrote:
> Hello, is there any way to get the templates as ANSI_378_2004 or
> ISO_19794_2_2005?
I'm afraid that nobody has implemented this in libfprint.
Cheers
___
fprint mailing list
fprint@lists.freedes
On Thu, 2019-05-09 at 18:09 +0900, Seong-Joong Kim wrote:
> I am really sorry to bother you.
> I didn't mean it.
>
> As you know, I've reported this issue to upstream on Mar 6, but you
> did not reply to my report about a month.
That's because you were already spamming me, privately, about a numb
On Thu, 2019-05-09 at 10:36 +0900, Seong-Joong Kim wrote:
> Hi,
>
> I wonder whether disclosure of a fingerprint is a vulnerability or
> not.
> In short, please let me know whether disclosure of a fingerprint is a
> vulnerability or not, to accomplish freedesktop's goal of securing
> the usage of
On Thu, 2019-01-24 at 15:29 +, Taj Hussain wrote:
> Hello,
>
> Why you are sending these emails to my account ?
Because you subscribed to this mailing-list in the past. I've
unsubscribed you now.
If other folks are receiving unwanted e-mails, unsubscription
instructions are at the bottom of
On Thu, 2019-01-24 at 10:19 +0800, Dave.Wang wrote:
> Hi Bastien,
>
> Thanks for your detailed reply!
>
> Unfortunately, our "match on chip" device need to load template from
> disk, it does not have persistent storage..
>
> I think we will need your help as below to implement "update
> template
Hello Dave,
Sorry about the late reply.
On Wed, 2019-01-02 at 10:58 +0800, Dave.Wang wrote:
> Dear,
>
> We want to implement the primitive driver which will use our "match
> on chip" sensor.
> Our "match on chip" sensor has function which can update the template
> after obtaining matched result
Hey,
This is going to be one of the last releases before the 1.0 release. A
non-exhaustive list of changes due to happen before 1.0 is available
here:
https://gitlab.freedesktop.org/libfprint/libfprint/issues?milestone_title=1.0
I expect a number of other changes to also happen in other parts of
On Fri, 2018-12-07 at 14:46 +0200, Igor Filatov wrote:
> I think Dave means that the scanner would capture the print when the
> device is powered on. Not as instructed by a userspace driver, but as
> a "hardware feature" of the button/sensor itself.
Which might need to be enabled in the hardware.
Hey Josh,
On Thu, 2018-08-16 at 20:14 +0100, Josh Holland wrote:
> Hi,
>
> I was trying out my fingerprint sensor (EgisTec ES603) with fprint-
> demo, and I noticed that fairly often the image produced when
> verifying is twice as tall as normal, and the bottom half contains
> only some long vert
Hello Dave,
On Wed, 2018-11-14 at 10:13 +0800, Dave.Wang wrote:
> Dear Bastien,
>
> Thanks for your quick reply!
>
> Feeling sorry for not indicating clearly about our definition of SSO
> In our definition of SSO,
What I was saying is that you shouldn't be using "SSO" as a name, it's
already so
t
library, so drivers cannot be proprietary. So the answer to that
question is no, given that the premise is incorrect.
Cheers
> Although it may need to create more APIs between libfprint and
> libfprint driver
>
> Best regards
>
> -----Original Message-
> From: Bastien
Hey,
On Tue, 2018-11-13 at 14:50 +0800, Dave.Wang wrote:
> Dear,
>
> I did some experiments as below:
> 1. I found that it is necessary to choose which account to login
> first before identifying the corresponding finger.
> 2. After I choose “account A”, I can’t identify the fingerprin
On Sat, 2018-09-29 at 10:04 -0600, Richi Plana wrote:
> Thanks. I'll bite and get the USB IDs. In case it isn't (and it seems
> likely since Synaptics' vendor ID isn't on the list),
It's there, under the name "Validity":
https://www.zdnet.com/article/synaptics-acquires-validity-for-255m-dives-int
Hey,
On Sat, 2018-09-29 at 02:38 -0600, Richi Plana wrote:
> Hi,
>
> I'm thinking of purchasing the Tt eSPORTS Black FP mouse with
> fingerprint scanner/reader
> (
> https://www.ttesports.com/Mice/233/Black_FP/productPage.htm?a=a&g=ftr)
>
> and am wondering if the list knows if the scanner is
On Thu, 2018-09-13 at 09:45 +0800, Josh.Chen wrote:
> Hi,
>
> Because NBIS does not work well on smaller images
> If there are no suitable open source image processing alternatives
> Is it possible alternative to a proprietary library?
Absolutely not, libfprint is and needs to remain free softwa
On Thu, 2018-08-30 at 11:10 +, Kleyson de Sousa Rios wrote:
> Hi Bastian,
>
> Is the below possible ?
> Keep the finger on the reader for more time before the image be
> taken.
It depends on the driver. Most devices will send us a message when a
finger has been set down, for us to take the im
On Mon, 2018-08-27 at 20:16 +0700, Владислав Зелёный wrote:
> Пожалуйста, не пишите на эту почту. Как отписаться от рассылки?
I unsubscribed you.
___
fprint mailing list
fprint@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/fprint
On Mon, 2018-08-27 at 18:33 +0300, Timo Teras wrote:
> Hi
>
> On Mon, 27 Aug 2018 12:56:21 +0200
> Bastien Nocera wrote:
>
> > On Thu, 2018-08-23 at 13:19 +, Kleyson de Sousa Rios wrote:
> > > To test I'm basically using the examples/ tools, and seems that
On Thu, 2018-08-23 at 13:19 +, Kleyson de Sousa Rios wrote:
> To test I'm basically using the examples/ tools, and seems that the
> drive_data has the correct value 5.
Looks like the device's output isn't always encrypted. Timo, could you
check whether this change makes sense? Kleyson, could y
On Wed, 2018-08-22 at 19:02 +, Kleyson de Sousa Rios wrote:
> Hi Bastien,
>
> I figured out that if I comment out the following "if statement", to
> force the execution of the respective code, I get a non-encrypted
> image.
>
>
https://gitlab.freedesktop.org/libfprint/libfprint/blob/master/l
On Tue, 2018-08-21 at 17:47 +, Kleyson de Sousa Rios wrote:
> Hi,
>
> Should I open a Bug ticket ?
>
> What kind of information should I include in the ticket to help
> investigate/reproduce the issue ?
Ideally, you would test this using the current git master version, try
to find a version
Hey,
After merging Igor's Elan driver changes, I've been working on updating
the copy/paste NBIS software we use for fingerprint matching to version
5.0.0.
It compiles (or so the CI says) though with loads of warnings. It would
be great if somebody could test that this version is at least as
func
On Fri, 2018-08-10 at 13:27 +, Kleyson de Sousa Rios wrote:
> I'm trying to use libfprint with UareU 4000B
> DigitalPersona fingerprint readers running in a Ubuntu 16.04
>
> libfprint-dev/xenial,now 1:0.6.0-2 amd64 [installed]
> libfprint0/xenial,now 1:0.6.0-2 amd64 [installed]
Before anythi
On Sat, 2018-07-21 at 12:24 +0700, Владислав Зелёный wrote:
> Hello! I would like to know if the device can be supported in the
> future by Aсer Swift 3.
> ID 1c7a:0570 LighTuning Technology Inc.
> This device is built-in.
As per
https://gitlab.freedesktop.org/libfprint/libfprint/blob/master/HAC
On Sun, 2018-06-24 at 14:25 +0300, Igor Filatov wrote:
> Bastien,
>
> I've incorporated latest upstream changes so I could open a merge
> request but it looks like on gitlab I need a permission to do it. Or
> should I just send a patch?
You don't have rights to commit directly to the libfprint r
On Tue, 2018-06-19 at 12:49 +0200, Péter Gönczöl wrote:
> Hi,
>
> Is it possible to enroll and verify fingerprint images (bmp format,
> grayscale) with libfprint?
> I've been reading the API docs and fprint.h but every functionality
> I'd need appears to be hidden from the applications.
>
> It se
On Mon, 2018-06-18 at 15:01 +0200, Hans de Goede wrote:
> Hi,
>
> On 18-06-18 14:58, Igor Filatov wrote:
> > I'd like to but I'm worried that people will have bad experience
> > with these devices (esp. 96x96 ones) and blame libfprint. And I
> > still haven't had the chance to pull in latest upstr
On Wed, 2018-01-17 at 15:11 +0100, Sébastien Béchet wrote:
> On 2018-01-17 12:12, Igor Filatov wrote:
> > Looks like o1ca as well https://github.com/iafilatov/libfprint/pull
> > /4
>
> Not o1ca but 0x0C1A. I create repository for POC:
>
> http://github.com/sbechet/elanfp
Any plans on sending tho
On Tue, 2018-06-12 at 15:46 +0200, Bastien Nocera wrote:
> Release notes and tarball are available at:
> https://gitlab.freedesktop.org/libfprint/libfprint/tags
And 0.8.1 is now out to fix a single missing character in the udev
rules installation ;)
Same
Release notes and tarball are available at:
https://gitlab.freedesktop.org/libfprint/libfprint/tags
Cheers
___
fprint mailing list
fprint@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/fprint
Hey,
On Mon, 2018-06-11 at 20:55 +, henry paul espinosa peralta wrote:
>
>
> Hello, dear
> I want to use this fingerprint capture device crosmatch verifier 310
> lc on unix system: ubunto 16.04 and raspbian strech
>
> ID 080b:0034 Cross Match Technologies
>
> ID del proveedor de USB
> 08
Hello again all,
Continous integration has been added to both libfprint and fprintd, so
that merge requests will be compile-tested before being committed.
We've also used the CI support to automate the creation of a new
website:
http://fprint.freedesktop.org/
For the record, the old website is h
Hey,
libfprint and fprintd have both migrated to gitlab.freedesktop.org:
https://gitlab.freedesktop.org/groups/libfprint
This means that driver authors should be able to fork the repository in
their personal area to work on a driver, and file MRs once the driver
is ready for review, which should
On Tue, 2018-05-29 at 19:57 +0300, Igor Filatov wrote:
> Looks like G_DEBUG_HERE is only available in glib >= 2.50. Might set
> the bar too high. For ex. latest Mint has 2.48 and the oldest Ubuntu
> LTS (14.04) only has 2.40. I think the latter could be a good
> baseline.
GLib 2.50 was released in
Hey,
In the process of writing and documenting the libfprint drivers API, I
realised that drivers have access to library internals for no good
reason, so I split off the internal library API from the drivers API.
If you have an out-of-tree driver, the easiest would be to update your
fork, and see
On Fri, 2018-05-18 at 09:49 +0300, Igor Filatov wrote:
> > From the user's perspective, users shouldn't have to build their
> own
> > system libraries. From the developers point-of-view, the rules are
> > actually readable, understandable, and it takes as long to build
> > libfprint and the docs as
ut it won't let me
> sign in. Says my account is blocked...
There's no new repo, it's not migrated yet.
> On Thu, May 17, 2018 at 7:01 PM Bastien Nocera
> wrote:
> > Hello all,
> >
> > libfprint has been ported to Meson[1] (from autotools) and gtk-doc
>
Hello all,
libfprint has been ported to Meson[1] (from autotools) and gtk-doc
(from Doxygen) in git. This means that building libfprint is now much
much faster, and the API documentation is now clearer.
It would be great if driver authors could update their development
branches and report any pro
On Thu, 2018-05-10 at 20:54 +0200, Julien Nicoulaud wrote:
> Hi,
>
> The supported devices list
> (https://www.freedesktop.org/wiki/Software/fprint/libfprint/Supported
> _devices/)
> has "MicrosoftKeyboard with Fingerprint Reader" as supported, but it
> also says "Last edited Fri 13 Sep 2013", so
On Fri, 2018-04-20 at 09:42 +0200, blob blob wrote:
> I'm using tis package for debian 9:
> Package: libfprint-dev (1:0.6.0-2 and others).
Please try not to use HTML email, you just yelled the version number at
us in huge print.
In libfprint 0.7 there's this item in the NEWS file:
Autodetect whet
On Thu, 2018-03-15 at 19:52 +, Mike wrote:
> Hi guys,
>
> I'm a total newbie to mail lists, so hope this is ok..
>
> I like to add support for my HP EliteBook 2560p fingerprint reader
> and just started to look for Linux support, since I'm now running a
> dual boot environment with Windows
On Tue, 2018-03-06 at 12:04 +0300, enock tum wrote:
> I have implemented the libfprint on my linux and it is working
> perfectly. The problem comes when i want to transfer the project to a
> windows based server, it tells me that jlibfprint.dll not found and i
> cant seem to get a fix in the whole
On Mon, 2018-01-08 at 17:19 +0100, TeEmZe wrote:
> Hello developers,
>
> I have a question regarding the libfprint library. I have a Xiaomi
> notebook with a fingerprint reader from Elan Microelectronics Corp
> (device 04f3:0c1a) running on Ubuntu. I already tried multiple
> packages for using it
On Tue, 2017-12-12 at 08:41 +0100, Hans de Goede wrote:
> Remove 2 entries from the whitelist for finger-print models for which
> we have a driver now, so they no longer need to be on the whitelist.
All 3 merged. In the future, please file those in the Freedesktop
bugzilla. Mailing-lists are dread
On Sat, 2017-11-25 at 10:48 +, Gnappino Gnappino wrote:
> Hi everyone, I'm relatively new to the linux world, or rather, I've
> been
> using it for so many years to develop, but I'm just trying to
> contribute
> to linux development now.
>
> I would like to do fprintd tests to improve the in
fprintd 0.8.0 is out
new in version 0.8.0:
- Lockdown the daemon to minimise potential security issues
- Don't wake up readers when there's no enrolled fingerprints
http://people.freedesktop.org/~hadess/fprintd-0.8.0.tar.xz
Cheers
___
fprint mailing li
Hey Kristaps,
On Thu, 2016-12-29 at 19:56 +0200, Kristaps Dzonsons wrote:
> Hi,
>
> Enclosed are two patches required for OpenBSD6.0 and current
> libfprint.
>
> The first is just for missing errno values. (FreeBSD is also patched
> at
> least for the ETIME.) These are directly from the OpenBS
On Tue, 2016-12-27 at 18:45 +0100, emak wrote:
> Hi
>
> I wanted to enter whether the password or use the fprint-reader. As
> the
> fprint-reader is not alwas faster (e.g. remote login / close laptop
> lid
> in docking station) I set this default order in my /etc/pam.d/system-
> auth:
> auth suffi
On Sun, 2016-11-27 at 16:59 +0100, Matthieu Vieira wrote:
> Hi,
>
> I recently bought an Acer Swift 3. There's a LighTuning Fingerprint
> reader but it doesn't work on Fedora 25 (and more on all
> distributions I tested).
> fprintd-enroll says that there is no device availables.
>
> lsusb give th
On Sun, 2016-11-27 at 21:14 +0100, Cedric Viou wrote:
> Hi,
>
> My HP ZBook provides a Validity fingerprint reader that is not yet
> supported by fprintlib:
> Bus 003 Device 003: ID 138a:003f Validity Sensors, Inc. VFS495
> Fingerprint Reader
>
> I run libfprint 1:0.6.0-git20160719-1-0ppa1~xenial
Heya,
A new version with an old bug fix.
version 0.7.0:
- Fix crash in the daemon when cancelling PAM conversation
- Fix build warnings and update translations
http://people.freedesktop.org/~hadess/fprintd-0.7.0.tar.xz
Cheers
___
fprint mailing list
f
On Mon, 2016-09-05 at 12:26 +0200, Salvo Tomaselli wrote:
> Bus 001 Device 006: ID 138a:0017 Validity Sensors, Inc. Fingerprint
> Reader
>
> Can be found on some newer thinkpads. I have a T560.
>
> I think you should update the page because there is a lot of outdated
> information around about Va
On Sat, 2016-08-27 at 14:59 -0400, Michael Phillips wrote:
> Hi,
>
> I see in pam/fingerprint-strings.h there is a 'any' finger. I was
> wondering if there is any way to get pam_fprintd to check against all
> enrolled fingers for the user instead of just the first/default
> finger, which is the ri
On Tue, 2016-01-12 at 09:52 +0100, Ricardo Ribalda Delgado wrote:
> Hello Jose
>
> Did you bother to go through the fp_img structure? Perhaps you should
> do some static analysis of the code instead of hoping that somebody
> else will do your work.
There's really no need to take that tone when re
Hey Jason,
On Fri, 2015-08-21 at 15:45 -0600, Jason Gerard DeRose wrote:
> As part of helping me understand the libfprint code, I ran scan-build
> and fixed one NULL pointer dereference it reported, which after
> tracing
> that back led to another small fix.
>
> 0001_fix_NULL_pointer_dereference_
On Tue, 2015-04-14 at 14:31 +0300, Olli Syrjälä wrote:
> Sorry if this is asked before, I tried this howto:
> http://tryitnw.blogspot.de/2013/02/easy-steps-to-enable-finger-print.html
> and it ended up that way that I can get sudo rights just with
> rerolling and then using them without knowing
On Wed, 2015-04-01 at 16:00 +0530, Prasanna Venkadesh wrote:
> Hi,
>
> I have downloaded the source of libfprint-0.6.0 and fprint-0.6.0.
> Compiled them and installed.
>
> fprintd-enroll enrolls the first entry, but keeps on waiting for
> next 4 enrolls. No feedback from the program either.
fp
Hey Carlos,
On Fri, 2015-02-06 at 17:22 +0100, Carlos Olmedo Escobar wrote:
> Signed-off-by: Carlos Olmedo Escobar
We don't use signed-off-bys. We also prefer patches to be attached to
bugzilla, this avoids them getting lost.
I've however committed this one.
Cheers
> ---
> libfprint/drivers/
On Tue, 2015-02-03 at 17:25 -0200, Bruno Medeiros wrote:
>
> > It seems to be a bug since 2008 but mostly unnoticed due to doing
> only that one enrollment.
>
>
> I had this strange behaviour for a long time in my UrU4000B, but it
> happens only on Ubuntu, with the same version of libfprint. I n
On Tue, 2015-02-03 at 19:11 +0200, Timo Teras wrote:
> On Tue, 03 Feb 2015 17:31:50 +0100
> Bastien Nocera wrote:
>
> > Any chance you could get this in git-formatted format with an
> > explanation of what it fixes in the state machine?
>
> I thought I already did t
Hey,
libfprint NEWS
--
2015-02-03: v0.6.0 release
* Drivers:
- Reduce duplication between AES3500 and AES4000 drivers and
add support for AES3500 device
- Add support for UPEK 147e:2020 and Upek Eikon 2 devices
- Add EgisTec ES603 driver
- Add VFS5011 driver
- Always p
On Wed, 2014-06-25 at 09:06 +0300, Timo Teras wrote:
> On Tue, 24 Jun 2014 22:01:24 +0200
> Martin Hejnfelt wrote:
>
> > Here's the output, this is just the examples/enroll.c which does the
> > same as my own app (which is using async calls).
> > I've inserted the "* * * " output via fp_dbg just
On Thu, 2014-10-30 at 15:42 -0400, Alexander Martin wrote:
> Hi fprint community!
>
>
> I am interested in using this tool and was curious about the type of
> image that is returned from the fingerprint reader. Is it JPG, PNG,
> WSQ, etc.?
They're returned in a format that's specific to each dev
On Tue, 2014-10-28 at 18:54 -0400, Brian Bouterse wrote:
> I have a ThinkPad T530 laptop. I have installed libfprint, fprintd,
> and the demo example on Fedora 20. I was able to run the demo, and it
> showed me the GUI. However at the bottom I see 'Status: No devices
> found'.
>
>
> I believe I h
On Wed, 2014-10-08 at 18:06 +0530, Shivaprasad Imdapur wrote:
> Hello,
>
>
> In my android device development project, I have hardware and I
> have developed driver for that. This hardware is placed using SPI
> drivers. Now I am able to scan a finger and get a raw data.
>
>
>My questio
Hey,
On Thu, 2014-09-04 at 14:29 +0200, Aydoğan Ersöz wrote:
> Dear fprint community,
>
>
> I'm working on a microcontroller project which embeds Fujitsu
> MBF900PFW imaging sensor on it. The microcontroller that I'm using is
> STM32F417IGH6. It has 1MB of flash memory and 196KB of RAM.
>
> I'm
On Fri, 2014-06-06 at 01:23 +0300, golden cut wrote:
> Hi,
>
>
> Couple of questions and suggestions from a new user.
>
> Is it the normal behavior of fprint to show no feedback when
> fingerprint is un/successfully scanned (at login, xscreensaver etc)?
> Should the user have to press enter fo
On Sun, 2014-04-06 at 01:49 +0200, Mariusz Ciszewski wrote:
> > I am currently working on a unit where I need fingerprint
> > identification of up to 50 users
>
>
>
> Hello Martin
>
>
> Please let us know how it will work. You wrote you need
> identification, so verification (ready to use fpr
> On Fri, Apr 4, 2014 at 9:28 AM, Bastien Nocera wrote:
> > On Fri, 2014-04-04 at 08:18 +0200, Mariusz Ciszewski wrote:
> >> For install new Fprintd V_0_5_1 to replace old from current Debian
> >> repository I need:
> >>
> >>
> >> Download s
On Fri, 2014-04-04 at 08:18 +0200, Mariusz Ciszewski wrote:
> For install new Fprintd V_0_5_1 to replace old from current Debian
> repository I need:
>
>
> Download sources from:
>
> http://cgit.freedesktop.org/libfprint/fprintd/snapshot/V_0_5_1.zip
>
> or
>
>
> http://cgit.freedesktop.org/li
On Tue, 2013-11-19 at 23:30 +0300, Vasily Khoruzhick wrote:
> On Tue, Nov 19, 2013 at 11:00 PM, Vinícius Souza
> wrote:
> > Hi Vasily, over here http://vini.w.pw/enrolled(microsoft).pgm and here
> > http://vini.w.pw/enrolled.pgm
>
> Hi Vinícius,
>
> I guess uru4k driver was broken for your devic
On Wed, 2013-10-23 at 21:28 +0200, Vojtěch Polášek wrote:
> Hi,
> OK, I still don't know what is wrong.
> I used fprintd-enroll for enrolling my fingerprint as my normal user as
> well as root.
>
> Here is my /etc/pam.d/common-auth
> auth[success=3 default=ignore]pam_fprint.so
That's sti
On Wed, 2013-09-25 at 22:26 +0200, Emile Nijssen wrote:
> Hey all,
>
>
> I'm writing a simple application for my front door, and would like to
> register many people.. however, the current API seems to only allow
> one person with 10 fingers.
>
>
> Is there an easy way to just 'keep registering
Em Thu, 2013-09-12 às 23:43 +0200, Vojtěch Polášek escreveu:
> When using fprintd-enroll, everything works, but when doing sudo, it
> prompts me for a password first and when I just press enter, it says,
> that no fingerpint could be found in the hardware.
Please quote the exact error message (in
Em Mon, 2013-04-01 às 12:43 +0200, Milan Lazecky escreveu:
> Thank you both.
>
>
> Ok, I have installed gdk-pixbuf (version 0.22) from ATrpms.
The current version is gdk-pixbuf 2.28. libfprint won't compile against
this 11-year-old version.
> Imagemagick libs were already installed (including
On 22 Mar 2013, at 00:10, Peter Eckersley wrote:
> I don't know if PAM creates obstacles to fixing these...
It's purely a PAM issue. gnome-shell uses two concurrent PAM stacks to work
around those limitations.
Those problems have nothing to do with fprintd, only pam_fprintd and the PAM
stack.
On Wed, 2013-01-30 at 12:07 -0430, newzenca wrote:
> Hello.
>
> i get this problem
>
> [newzen@i5Desk v_0_5_0]$ make
> drivers/aes1610.c: En la función ‘capture_read_strip_cb’:
> drivers/aes1610.c:619: error: declaración implícita de la función
> ‘g_slist_free_full’
You need GLib 2.28 or newer.
On Thu, 2013-01-24 at 09:39 +0300, Vasily Khoruzhick wrote:
> On Thu, Jan 24, 2013 at 8:43 AM, Moritz von Schweinitz
> wrote:
> > Ok, I disabled ALL the 'aes' drivers (because of compiler errors), and
> > now the examples 'verify' and 'enroll' which are included seem work.
> > fprint_demo still do
On Tue, 2013-01-15 at 11:57 -0200, Daniel Neis Araujo wrote:
> Ok,
>
>
> here is what i did (i am using x86_64 as host):
>
>
> * used qemu to boot an ubuntu for arm
> (https://wiki.ubuntu.com/ARM/RootfsFromScratch)
>
> * build libfprint as on x64_86
>
> * build the examples
>
> * started som
On Mon, 2013-01-14 at 23:40 -0200, Daniel Neis Araujo wrote:
> Hello,
>
> i've tried to run a compiled version of libfprint 0.5.0 for ARM on an
> Android environment, but it didn't work.
> I would like to here from the more experienced with libfprint if this
> is the way to go or there are simpl
Em Thu, 2012-12-06 às 22:47 -0600, Ing. Alfredo Alarcon escreveu:
> Hi everybody, i have a 400b digital persona sensor, when i used the sdk
> from digital persona (before they charged it) the identify function wait
> for a finger n milliseconds and then break the function and continue
> with the
Heya,
A new version of libfprint is available for download at:
http://people.freedesktop.org/~hadess/
Here are the major changes from the 0.4.0 release over a year ago. Many
thanks to Vasily Khoruzhick for the hard work on writing and updating
the majority of those fingerprint drivers.
* Driver
On Tue, 2012-11-06 at 18:06 -0600, Ing. Alfredo Alarcon wrote:
> Hi, sorry for my bad english, my name is Freko from Mexico, have a 4000b
> reader and a Beaglebone ARM 7 with Ubuntu 12.04 and kernel 3.2.
> I successfully installed libfprint from sources and all dependencies
Which "sources" did
On Tue, 2012-11-06 at 12:30 +0400, Yuri Kozlov wrote:
> В Tue, 6 Nov 2012 14:27:23 +0800
> YANG Yang пишет:
> >
> > then it reported:
> >
> > /usr/local/arm/4.3.2/bin/../lib/gcc/arm-none-linux-gnueabi/4.3.2/../../../../arm-none-linux-gnueabi/bin/ld:
> > cannot find -lssl3
> > collect2: ld return
On Mon, 2012-10-15 at 11:44 +0100, Simon Kenyon wrote:
> On 10/15/12 11:10, Vasily Khoruzhick wrote:
> > On Mon, Oct 15, 2012 at 12:48 PM, Bastien Nocera wrote:
> >
> >>> Actually, it was possible to reverse engineer AES2550 protocol and use
> >>> same
On Mon, 2012-10-15 at 13:10 +0300, Vasily Khoruzhick wrote:
> On Mon, Oct 15, 2012 at 12:48 PM, Bastien Nocera wrote:
>
> >> Actually, it was possible to reverse engineer AES2550 protocol and use
> >> same driver for
> >> AES2810 (according to datasheet AES25
On Sat, 2012-10-13 at 11:09 +0300, Vasily Khoruzhick wrote:
> On Sat, Oct 13, 2012 at 7:50 AM, Anton Krug wrote:
> > Hi
>
> Hi Anton
>
> > I found the remark that the "less safe" mode is available, l'm little bit in
> > awe. I was in belive that there is just the crypto mode and AuthenTec
> > wo
On Mon, 2012-10-15 at 11:40 +0200, Bastien Nocera wrote:
> On Thu, 2012-10-11 at 16:13 +0300, Vasily Khoruzhick wrote:
> > On Mon, Oct 8, 2012 at 6:30 PM, Bastien Nocera wrote:
> > > On Mon, 2012-10-08 at 18:20 +0300, Vasily Khoruzhick wrote:
> > >> Hi Bastien,
&g
On Thu, 2012-10-11 at 16:13 +0300, Vasily Khoruzhick wrote:
> On Mon, Oct 8, 2012 at 6:30 PM, Bastien Nocera wrote:
> > On Mon, 2012-10-08 at 18:20 +0300, Vasily Khoruzhick wrote:
> >> Hi Bastien,
> >>
> >> > Finally, patches should go to Bugzilla (bu
On Wed, 2012-10-10 at 18:47 +0300, Vasily Khoruzhick wrote:
> Bastien, I've attached patch to
> https://bugs.freedesktop.org/show_bug.cgi?id=50859
>
> Could you please review it?
I already receive the mails, no need to send me an extra mail.
Cheers
__
On Tue, 2012-10-09 at 09:13 +0530, Kunal Gangakhedkar wrote:
> Resending - since earlier mail got blocked from the list due to size
> >40KB.
>
>
>
> On Monday 08 Oct 2012 5:54:06 PM Bastien Nocera wrote:
>
> > On Mon, 2012-10-08 at 21:03 +0530, Kunal Gangakhed
On Mon, 2012-10-08 at 21:03 +0530, Kunal Gangakhedkar wrote:
> On Monday 08 Oct 2012 4:50:20 PM Bastien Nocera wrote:
> >
> > Thanks for the patches, but you haven't explained why we would want or
> > need this feature. libfprint has no internal API guarantees, and is
&
On Mon, 2012-10-08 at 18:20 +0300, Vasily Khoruzhick wrote:
> Hi Bastien,
>
> > Finally, patches should go to Bugzilla (bugzilla.freedesktop.org), not
> > the mailing-list.
>
> Out of curiosity, why?
>
> It's easy enough to apply patch from mailbox, it's much easier to
> review patches and comme
Hey Kunal,
On Mon, 2012-10-08 at 20:09 +0530, Kunal Gangakhedkar wrote:
> This is a set of patches that tries to build the drivers as shared object
> modules and provides API to load/unload them on the fly.
>
> The design is inspired by the way linux kernel implements modules -
> albeit, with a l
Hey,
On Wed, 2012-10-03 at 16:01 -0700, Keaton Mowery wrote:
> Hi all,
>
> I'm seeing a very odd crash while using libfprint's async API. Here's
> a backtrace:
>
> -
> Program received signal SIGSEGV, Segmentation fault.
> 0xb4e14211 in __pthread_mutex_unlock_usercnt () from
> /lib/i686/
Hey Timo,
Em Tue, 2012-09-25 às 16:02 +0300, Timo Teras escreveu:
> Hello list,
>
> I have reverse engineered the uru4500 encryption scheme from the binary
> only drivers. And I have a modified libfprint here that gives sensible
> data from this device - fprint_demo seems to work with it just nic
1 - 100 of 133 matches
Mail list logo
