; > fprint-ow...@lists.freedesktop.org
> >
> > When replying, please edit your Subject line so it is more specific
> > than "Re: Contents of fprint digest..."
> >
> >
> > Today's Topics:
> >
> > 1. Re: How to writ
On Sat, 2024-03-23 at 18:42 +, Andy Doddington wrote:
>
>
>
>
> >
> >
> >
> >
> > Dear All,
> > I note from the documentation
> > at https://fprint.freedesktop.org/libfprint-dev/intro.html that:
> > "This documentation is not aimed at developers wishing to develop
> > and , contribute f
cluster < known
> Universe
> - There are 10 types of people in this world: those who understand
> binary and those who don't
> - There is NO CLOUD, just other people's computers
> - There is NO INTELLIGENCE in AI, just huge knowledge and deep
> statistics
>
>
>
Hi,
On Fri, 2024-03-22 at 15:52 +0100, Eric J.P.E. Davanture wrote:
>
> Greetings,
>
> I have SuSE Linux Enterprise Desktop (SLED) 15 SP5 and I use KDE
> Plasma X11 with fprintd package installed (v 1.94.2-bp155.2.3.1) to
> unlock the desktop using the integrated fingerprint reader of an HP
>
On Thu, 2022-12-01 at 12:41 +, Danial Mahmoud wrote:
> Hello!
> I'm using libfprint to program a DigitalPersona 4500 reader on a
> Raspberry Pi.
I think that is an image device (at least that is how libfprint seems
to use it in the uru4000 driver).
Which means, the data returned by libfprint
On Mon, 2022-04-04 at 08:20 +, Roosembert Palacios wrote:
> Hello o/
>
> I'm trying to write an ssh-askpass replacement that requires fingerprint
> authentication. I looked at the sources of fprint-verify to learn about
> the protocol with dbus, but when I call GetDefaultDevice on the manager
On Wed, 2022-03-23 at 17:06 +, Charlie Lin wrote:
> Asking for a bit of advice. My fingerprint scanner communicates via UART, and
> apparently the existing helper functions only work for fingerprint scanners
> that communicate via USB or SPI. If I need to create such helpers for UART,
> how sho
Hi,
It isn't supported and most likely could only be supported if the
community reverse engineers the protocol.
Some of the Synaptics readers are supported by Synaptics. However, that
only applies to a specific subset of chipsets that also have a firmware
with Linux support.
Benjamin
On Sat, 20
Hi,
I released 1.94.0 for both. The major change in this release is
suspend/resume support via systemd-logind. If the driver and hardware
support it, then interactive operations can run over suspend,
automatically resuming the laptop if a finger was presented.
For this to work correctly, the "pow
ice Update via fwupd.
>
> Albert
>
> On 7/23/21 5:46 PM, Benjamin Berg wrote:
> > Hi,
> >
> > have you double checked that you have the latest firmware installed
> > by
> > using fwupd?
> >
> > Benjamin
> >
> > On Fri, 2021-07-23 at 1
Hi,
have you double checked that you have the latest firmware installed by
using fwupd?
Benjamin
On Fri, 2021-07-23 at 17:08 +0200, Albert Schimpf wrote:
> Hello everyone.
>
> I'm trying to get the fingerprint reader to work on my HP g7 435
> laptop,
> 5.13.4-arch1-1 kernel.
> The fingerprint
Hi,
I pushed out 1.92.0 releases for both libfprint and fprintd. There are
some larger changes included. Please see the NEWS for more details.
libfprint:
https://gitlab.freedesktop.org/libfprint/libfprint/-/releases/v1.92.0
fprintd:
https://gitlab.freedesktop.org/libfprint/fprintd/-/releases/
er thread.
>
> Thanks for your support.
>
> From: Benjamin Berg
> Sent: Wednesday, April 21, 2021 3:30 AM
> To: Carlos Garcia; fprint@lists.freedesktop.org
> Subject: Re: [fprint] Memory management Libfprint
>
> Hi Carlos,
>
> the image returned by fp_d
On Thu, 2021-04-22 at 11:38 +0200, Benjamin Berg wrote:
> I'll submit a fix later, but just keeping the FpContext around (or
> unref'ing it only after the "device-removed" signal has happened)
> should work around the problem.
Or just doing
while (g_main_c
in
>
> The library works fine when the device is reconnected, but I want to
> know about these 2 errors
>
>
> Do you know what happens?
>
> And a final question related to g_idle_add
>
> When g_cancellable_cancel is invoked, it needs to be invoked with
> g_idl
Hi Carlos,
the image returned by fp_device_capture_finish is owned by your code
(marked as "transfer full"). It is a GObject, and you are responsible
to eventually call g_object_unref on it.
There are various ways of achieving that. If you can use the modern
GLib autoptr features, then I would su
Hi,
On Wed, 2021-04-14 at 16:04 +, Carlos Garcia wrote:
>
> Hi everyone.
>
> I have problems with g_main_loop_runexecuting it in another thread.
> I’m using a Digital Persona U are U 4500 device.
>
If you have the g_main_loop_run running in a different thread, then
*all* calls into libfp
Hi,
we have two main error domains inside libfprint. Those are
FP_DEVICE_RETRY and FP_DEVICE_ERROR which identify soft errors and hard
errors.
We do however currently expose the underlying error from e.g. libusb if
such an error occur. Any such error needs to be be considered
equivalent to FP_DEV
Hi,
Unfortunately, I believe that the 27c6:5395 device specifically uses a
proprietary encryption scheme.
There has been some reverse engineering work (including promising work
for i2c devices from goodix). That might be a good starting work, but I
expect more reverse engineering would be requir
Hi,
these readers are generally USB and writing a driver is easy purely
from a communication point of view.
However, the hard part is understanding the USB protocol. This requires
reverse engineering. As these are security devices, they usually are
much more complicated and are cryptographically
Hi,
adding the list back to CC, as I don't see a reason to exclude them.
On Thu, 2021-02-04 at 14:18 -0300, Anderson Marques wrote:
> Benjamin Berg, sorry to bother, compiled version 1.90.7, had
> libfprint-dev 1: 0.8.2-3 installed, now displays the following in
> python when
On Thu, 2021-02-04 at 08:46 -0300, Anderson Marques wrote:
> Good morning, I am getting the following error
> /home/pi/biometria/venv/lib/python3.7/site-packages/fprint.cpython-
> 37m-arm-linux-gnueabihf.so: undefined symbol:
> fp_driver_supports_imaging, I think it is the python version, i'm
> usi
Hi,
it depends on the device, and you cannot tell from the USB PID
directly.
For the synaptics driver to work, two conditions need to be met:
1. It needs to be one of the more advanced match-on-chip devices
(I believe the chipset is codenamed Prometheus)
2. The firmware of that device needs
Hi,
On Mon, 2021-01-18 at 16:07 +, Carlos Garcia wrote:
> [SNIP]
> I made a port of libfprint for Windows O.S. using MSYS2 and works
> fine. I have tested the examples provided in the library v1.90.6 for
> the enroll and verify processes in Linux (Ubuntu 18.04 LTS) and
> Windows using the dev
Hi,
as you may have noticed, there were a number of fprintd and libfprint
releases in a row. The mess should be over with now, but let me explain
a bit what and why it happened.
The main regressions triggering new releases were:
* libfprint auto-suspending a USB hub
-> This was caused by a us
t would be good if I talk to Merlin/PixelAuth directly?
Then we can maybe also figure out how to get the driver into a
mergeable state.
If it helps, I am also happy for us to have a call to discuss
everything.
Benjamin
> On Wed, 07 Oct 2020 13:11:03 +0300 Benjamin Berg <
> benja.
Hi Furkan (and anyone at PixelAuth),
On Tue, 2020-09-15 at 16:44 +0300, Furkan Salman wrote:
> I have been working with PixelAuth developer who have a new
> fingerprint sensor with match-on-chip with storage capacity of 16
> fingers.
Sorry if I didn't have a closer look at the code yet.
> We ha
expect a few issues and room for improvement, so
any feed back is explicitly welcome.
Benjamin
On Tue, 2020-05-12 at 13:45 +0200, Benjamin Berg wrote:
> Hi,
>
> just a heads up that I have started doing work on adding support for
> the Secure Device Connection Protocol (SDCP)[1] as
reach the person managing the list at
> > fprint-ow...@lists.freedesktop.org
> >
> > When replying, please edit your Subject line so it is more
> > specific
> > than "Re: Contents of fprint digest..."
> >
> >
> > Today's To
Hi,
I have released libfprint version 1.90.3:
https://gitlab.freedesktop.org/libfprint/libfprint/-/releases
This release mostly contains support for a number of new match-on-chip
devices. Most notable is the addition of the new goodixmoc driver.
Currently the driver has the small caveat that we h
On Fri, 2020-06-12 at 22:08 +0700, Indev wrote:
> What is the state of small sensors matching? Are there any working
> drivers for small sensors?
I think the equivalent case here is the elan driver. It continues to
grab more image frames assuming that the user is swiping the finger
over the sensor
Hi,
On Mon, 2020-06-08 at 14:20 +0200, Benjamin Berg wrote:
> Highlights:
> * A patch for nbis required for some sensors was accidentally dropped in
>an earlier release. Users of these sensors/drivers (aes1610, aes2501,
>aes2550, aes1660, aes2660, elan, upektc_img) need
Hi,
I have released libfprint version 1.90.2:
https://gitlab.freedesktop.org/libfprint/libfprint/-/releases
sha256sum of the uploaded tarball is:
f126b37c036ead4b4711d1a305bbd75de4041ec95b3fa376a2d1a95a40eab578
libfprint-1.90.2.tar.xz
Benjamin
Release Notes:
This release contains a large amo
Hi,
just a heads up that I have started doing work on adding support for
the Secure Device Connection Protocol (SDCP)[1] as designed by
Microsoft.
I do not know whether there are currently devices out there that can
already be supported with an SDCP implementation in libfprint. However,
I am pret
Hi,
I have released libfprint version 1.90.1:
https://gitlab.freedesktop.org/libfprint/libfprint/-/releases
sha256sum of the uploaded tarball is:
bd03dd5e95db32d8cd3e5c91c582a0cdc634a14c20c419ac06b1445150d366df
libfprint-1.90.1.tar.xz
Benjamin
Release notes:
This release fixes a lot of the
Hi,
I have released libfprint version 1.90.0:
https://gitlab.freedesktop.org/libfprint/libfprint/-/releases
This version breaks API and ABI to previous versions. The API is
intended to remain stable at this point, however, this will only be
guaranteed from 2.0 onwards.
930f530df369ff874d7971f0b7
Hi,
we are currently finalizing libfprint version 2 beta release. As there
may be some out-of-tree drivers, I'll attach the coccinelle/spatch
files I used for driver porting. This may be of interest to some people
and should help porting further drivers in the future.
Note that these semantic pat
t new driver.
> --
> Best Regards,
> Mozammel Hossain
> M: +95 9786256424
>
>
> On Mon, Aug 12, 2019 at 7:28 PM Benjamin Berg <
> benja...@sipsolutions.net> wrote:
> > Hi,
> >
> > I am wrapping up the libfprint update, and I am also adding
>
can test it, that
would be useful.
Benjamin
On Wed, 2019-07-10 at 14:09 +0200, Benjamin Berg wrote:
> 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.
>
> Thi
> On Wed, Jul 10, 2019 at 2:24 PM Benjamin Berg <
> benja...@sipsolutions.net> wrote:
> > Hey,
> >
> > On Wed, 2019-07-10 at 14:21 +0200, Bastien Nocera wrote:
> > > > … Most drivers have been ported at this point (fixing a
> > > > number of i
Hey,
On Wed, 2019-07-10 at 14:21 +0200, Bastien Nocera wrote:
> > … Most drivers have been ported at this point (fixing a
> > number of issues in the process).
>
> Anything that could be backported? Failing that, an issue filed per
> problem would go a long way towards cleanups for 1.0.
There we
he callback function
* Changed error reporting (GError instead of pure integer)
Comments and feedback are welcome!
Benjamin
On Tue, 2019-06-18 at 10:48 +0200, Benjamin Berg wrote:
> I realised that I only had talked to a few individuals about this, so
> it seems like a good idea to infor
Hi,
I realised that I only had talked to a few individuals about this, so
it seems like a good idea to inform the ML about some of the ideas.
The current situation is that we are looking at adding support for
devices that store the print data in the sensor. With these devices, a
few new operation
43 matches
Mail list logo
