GitLab

If FP_DEVICE_EMULATION is set, then switch to using predictable EC
ephemeral key and random numbers. This should allow recording and
replaying real device interactions using umockdev.

This will allow creating a fixed key for testing

This device is designed to talk to an external executable. This
executable can be provided/created using the test implementation from
Microsoft.

This adds a base class for SDCP devices. Not all functionality has been
fully tested, in particular the code to verify the model certificate is
most likely broken or incomplete. One problem there is that there is no
code to find the root CA to trust.

See: #257

Throw a specific error when we are unable to verify the integrety of the
device.

For now it is identical to a RAW print. However, this is likely to
change in the future.

Just a minor change, but makes the file a bit more readable.

Devyn Cairns authored Nov 05, 2021 and Benjamin Berg committed Feb 11, 2022

The internal storage of this device can get messed up by other operating
systems, so it's handy to be able to clear it.

I'm not 100% sure whether the commands I've sent to the device are
exactly what is supposed to be used (just a guess), but it did seem to
work, and it even fixed another issue I had.

The API should return the recognized print, even if none of the prints
given in the gallery (or the one passed to verify) matched. Without this
the garbage-collection of left-over prints does not work, causing issues
after reinstall.

Fixes: #444

Prints may have an invalid date. Extend the checks so that this is also
caught in addition to a NULL date.

Otherwise you can't tell from the log whether parsing the body or header
failed.

In commit 5c28654d ("goodixmoc: Fix print template parsing") the length
check for the verify and duplicate check responses by requiring two
extra bytes at the end of the message.

There were also issues in other places where the length was not checked
correctly, including a scenario that could cause a read beyond the end
of the buffer.

Related: #444

New values taken from a newer version of the official driver.

* Allow FPI_PRINT_NBIS to be extended rather than overridden if a user
  supplies an existing FpPrint template with data;
* Prints will only be extended if a device has the required feature.
  For image-based devices this feature is added by default since they
  typically do not have storage (this can be overridden at the child
  class level).

Extending an existing FpPrint requires passing a template print with
existing data during the enrollment process. This is done because the
caller is responsible for maintaining the fingerprint database and doing
the necessary deserialization operations if needed. The existing
example program is updated to show how to do that.

Otherwise tightly looping SSMs (primarily SPI transfers), will flood the
logs in inappropriate ways.

Two of the printed variables were only calculated after the message was
printed, making the logged information less useful than it could be.

Benjamin Berg authored Nov 24, 2021 and Benjamin Berg committed Dec 01, 2021

This ensures that we have processed all hotplug events before
considering enumeration to be complete. This is important due to USB
persist being turned off. At resume time, devices will disappear and
immediately re-appear. In this situatoin, enumerate could first see the
old state with a removed device resulting in it to not be discovered.

As a hotplug event is semingly emitted by the kernel immediately, we
can simply make sure to process this hotplug event before returning
from enumerate.

Closes: fprintd#119

Added description and fixed incorrect name in comment, so now gtkdoc
actually shows useful information.

Benjamin Berg authored Oct 25, 2021 and Benjamin Berg committed Oct 27, 2021

The length is only a single byte in the transfer. However, the struct
had a uint32_t in that place, breaking the sizeof() calculation and
seemingly creating issues for certain lengths of user id strings (which
depend on the username).

Fix this by changing the type to uint8_t. Also add the initial 0x43
prefix byte and a byte of apparent padding that the struct contains.
Leave the two reserved bytes at the end, as they seem to actually have a
meaning (i.e. they are seemingly send in listings).

This effectively makes the struct one byte smaller, bringing it down to
127 bytes from 128 bytes.

Closes: #428, #404

This as per the same reasons of commit 63bfaf4f, and without trailing new
lines such attributes aren't picked by umockdev in ubuntu and debian.

63CC: Dell Latitude series fingerprint sensor

Signed-off-by: hermanlin <herman.lin@emc.com.tw>