GitLab

Add naive detection of image encryption: if stddev between two
adjacent rows is higher than threshold assume that image is encrypted
and decrypt it.

Fixes fd.o bug 88945

Its width is only 216 pixels, and it appears not to be enough for matching at
default threshold.

Use fpi_mean_sq_diff_norm() for blank line detection and
fpi_mean_sq_diff_norm() for duplicate line detection.
Fixes finger presence and removal detection.

New driver for 138a:0050 device

https://bugs.freedesktop.org/show_bug.cgi?id=91616

The code was indented, but only the first call was actually in the
conditional, which meant that initialisation carried on as normal on top
of a failed USB device. Exit early and remove the conditional to fix
this.

https://bugzilla.gnome.org/show_bug.cgi?id=98594

The code was indented, but only the first call was actually in the
conditional, which meant that initialisation carried on as normal on top
of a failed USB device. Exit early and remove the conditional to fix
this.

https://bugs.freedesktop.org/show_bug.cgi?id=98594

Debian's ash doesn't implement pushd/popd.

The device is already supported by the vfs5011 driver and non-
blacklisted, so will show up in the udev rules, but for ease of
backporting to older versions, add it to the whitelist anyway.

https://bugzilla.redhat.com/show_bug.cgi?id=1173367

Driver is not able to cancel imaging process without this change

It was here for aes2501 and aes1610 before moving assembling routines
into common code.

Height is not a good determinant in movement direction, normalized
error is much better. Should fix aes1610 and aes2501 driver issues.

Set partial flag to remove false minutiae at the perimeter of a scan

Set partial flag to remove false minutiae at the perimeter of a scan

Set partial flag to remove false minutiae at the perimeter of a scan

Set partial flag to remove false minutiae at the perimeter of a scan

Frame assembling routines are not aes-specific, so move them into a separate file
and add an accessor for peeking a pixel.

It seems that on faster devices, the driver can get more duplicate lines.
Without this change scan looks too stretched.

Suggested by: Thomas Rinsma <thomasrinsma@gmail.com>

Restart scan if core did not ask to terminate it explicitly.

Otherwise we end up in reporting the same result on next iteration.

Sensor can report "short scan" or "finger not centered" instead of image,
so it's necessary to handle them gracefully.

Smart sensors like Upek TouchChip Coprocessor can provide scan status instead
of image, as result we need to report such status as "short scan" or "finger not centered"
from within the driver, since it's not a session error.

Replace upekts_img with upektc_img

Sensor width seems to be only 128 pixels and that's not enough
for scanning whole finger surface. Lower bz3_threshold to 25,
since for wrong finger score never goes above 10, but sometimes
for right finger score is below 40.

Sensor width seems to be only 128 pixels and that's not enough
for scanning whole finger surface. Lower bz3_threshold to 20,
since for wrong fingerprint score never goes above 10, but sometimes
for right finger score is below 40.

And activate perimeter points removal if this flag is set.

Remove minutiae that are located on scan perimeter