baserev update by copy to link target

• Files Changed
• Browse Source

- add all supported USB devices as Supplements
(hopefully I did it right; list taken from the project page)

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

- Do not recommend lang package: the lang package has smarter
  supplements in place.

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

Update to version 1.94.2

• Files Changed
• Browse Source

- Add upstream bug fix patches, fix build with meson 0.60.x and
  newer:
  + f4256533d1ffdc203c3f8c6ee42e8dcde470a93f.patch
  + 2c34cef5ef2004d8479475db5523c572eb409a6b.patch

• Files Changed
• Browse Source

- Fix for openSUSE Leap 15.3, makro %{_pam_moduledir} is unknown in
  openSUSE Leap 15.3

• Files Changed
• Browse Source

• Files Changed
• Browse Source

• Files Changed
• Browse Source

new upstream release

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

- fix pyton dbus-python build dependency for Leap 15.3 boo#1183818

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

- Update to version 1.90.9
  * Fix multiple daemon lockup issues (#97)
  * Fix print garbage collection to not delete used prints
  * pam: Use the device with the most prints

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

- Update to version 1.90.8
  It seems that we are finally reaching the end of the tunnel with
  regard to regressions. One more issue that cropped up was that a
  pam_fprintd fix to avoid a possible authentication bypass caused
  issues when fprintd was just started on demand.
  Highlights:
  * pam: Only listen to NameOwnerChanged after fprintd is known to
    run.
  * Place new ObjectManager DBus API at /net/reactivated/Fprint

- Update to version 1.90.7
  While 1.90.6 fixed a number of issues, we did have a bad
  regression due causing pam_fprintd to crash when there are no
  fingerprint devices installed.
  Highlights:
   * pam: Guard strdup calls against NULL pointers

- Update to version 1.90.6

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

- Update to version 1.90.5
  The 1.90.5 release was unusable due to a number of inter-related
  issues with the DBus interface and authorization. We also found
  a number of problems with possible security implications.
  Currently fprintd will do interactive authorization even if this
  was not requested using the correct DBus method call flag. All
  API users MUST be updated to set the flag as it will be enabled
  in the future!
  Highlights:
   * Fix fprintd DBus configuration
   * Change details of what requires authorization
   * Fix various race conditions in pam_fprintd
   * Permit interactive authorization from fprintd utilities
   * Do not allow deletion while another operation is ongoing
- Drop patch:
  * 0001-tests-Fix-test-not-failing-on-error.patch

- Update to version 1.90.4
  The 1.90.4 release caused a major regression, as it included a
  USB hub in UDEV the autosupend rule list.
  Highlights:
  * Remove USB hub from udev autosupend rules
  * synaptics: Add PID 0x00c9 which is used in some HP laptops

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source