1. 21 Nov, 2008 9 commits
  2. 03 Nov, 2008 6 commits
  3. 02 Nov, 2008 11 commits
    • Bastien Nocera's avatar
      Always emit VerifyFingerSelected · 09852db6
      Bastien Nocera authored
      If the finger passed for verification is -1, always emit the
      VerifyFingerSelected signal, as the front-end isn't to know
      whether we're using identification or verification.
    • Bastien Nocera's avatar
      Fix a bunch of warnings · 35ae4dd0
      Bastien Nocera authored
      More warnings fixed in the file storage.
    • Bastien Nocera's avatar
      Fix another error path · 0a075532
      Bastien Nocera authored
      More to do though...
    • Bastien Nocera's avatar
      More identification work · 15fbacd7
      Bastien Nocera authored
      - Add a finger selected signal, so that when an "automatic" finger
        is selected for verification, we know which one to scan
      - Fix the finger print numbers list to use GPOINTER_TO_INT /
      - Make sure the gallery is NULL when there's no prints available
      - Don't use identification when a finger number is provided
      - Add support for selecting the finger number in verify
      - Add support for fatal warnings there as well
    • Bastien Nocera's avatar
      Add identify support · ee874bb1
      Bastien Nocera authored
      Passing -1 to the VerifyStart function will either accept any
      fingers scanned, if the driver supports identification, or select
      the first enrolled fingerprint for scanning if it doesn't.
    • Bastien Nocera's avatar
      Debug output cleanup · 974e022c
      Bastien Nocera authored
      Remove a few debug messages, and merge another one.
    • Bastien Nocera's avatar
      Rework the "SetUsername" functionality · e8c36e95
      Bastien Nocera authored
      - Remove SetUsername itself, and add a username parameter to DeviceClaim,
        ListEnrolledFingers and DeleteEnrolledFingers.
      - For each of those calls, check that the incoming connection is allowed
        to operate on that particular username
      - Don't require a claimed device to list or remove fingerprints
      - Clean up username and sender when releasing the device
      - Modify the storage backend to not require an opened device to list
        or delete fingerprints
      - Add a simple test program to list registered fingerprints for the
        usernames passed as argument
    • Bastien Nocera's avatar
      Update storage code to allow plugins · bd2debc0
      Bastien Nocera authored
      Add naive plugin support to the storage code, it will
      load plugins from $(libdir)/fprintd/modules, given the configuration
      from /etc/fprintd.conf.
    • Bastien Nocera's avatar
      Fix PolicyKit action for deleting fingerprints · c738aa33
      Bastien Nocera authored
      We can only delete fingerprints if we could enroll them
      in the first place.
    • Bastien Nocera's avatar
      Add DeleteEnrolledFingers · af42db88
      Bastien Nocera authored
      To delete all the enrolled finger prints for a particular user.
      We can already overwrite existing enrolled fingerprints, and there's
      not really any point in dismissing just one fingerprint.
    • Bastien Nocera's avatar
      Kill LoadPrintData and UnloadPrintData · bb121098
      Bastien Nocera authored
      They were just doing nothing interesting for us, and might
      cause problems if data changes under us (say, remote storage).
  4. 22 May, 2008 9 commits
    • Bastien Nocera's avatar
      Add PolicyKit checking · 46a9783b
      Bastien Nocera authored
      Add PolicyKit checks to all the public functions, grouped
      in 2 main groups: Verify and Enroll
      By default, only the user is able to enroll new fingers,
      or verify themselves.
      You need to be allowed at least one of those 2 actions
      to be allowed to claim or release the device.
      We also add a new SetUsername function, for administration
      functions. Users will need to be authenticate as admins to
      be allowed to change the username on which the actions will
      be taken. Any prints loaded before the change of username will
      be unloaded.
    • Bastien Nocera's avatar
      Start of PolicyKit support · 61a2266e
      Bastien Nocera authored
      Get a PolicyKit context per-device, set up its main loop,
      and steal more code from gnome-panel to check whether
      the actions are allowed for a particular caller.
    • Bastien Nocera's avatar
      The user that claims the device is the one we work on · 5e194488
      Bastien Nocera authored
      When the user claims the device, get its uid and username,
      and use this data to read/save from storage.
    • Bastien Nocera's avatar
      Save using storage · 8529a43b
      Bastien Nocera authored
      Save the fingerprint using the storage functions so we
      can verify the data we enroll.
    • Bastien Nocera's avatar
      Kill ListEnrolledFingersFromStorage · b1b5e2b4
      Bastien Nocera authored
      Last FromStorage variant killed, we need to make sure all
      the functions now use the storage functions internally,
      otherwise we won't be able to load from the place we save.
    • Bastien Nocera's avatar
      Constify username · 148b6fc6
      Bastien Nocera authored
      Fixes a few warnings on compilation
    • Bastien Nocera's avatar
      Kill LoadPrintDataFromStorage · 5d4e23ab
      Bastien Nocera authored
      First FromStorage variant to go
    • Bastien Nocera's avatar
      Fix return values for async methods · 7f592dd2
      Bastien Nocera authored
      Async methods should return "out" variables using dbus_g_method_return(),
      not through function parameters. Fixes crashing using those functions.
    • Bastien Nocera's avatar
      Async methods return void · c63f624a
      Bastien Nocera authored
      Thanks to Richard Hughes for spotting this. Shouldn't
      make any operational differences, as the return values
      of those methods weren't used anyway.
  5. 18 May, 2008 1 commit
    • Bastien Nocera's avatar
      Add user tracking when claiming a device · 1748e5f4
      Bastien Nocera authored
      Mark all the methods on the device as async, so we
      can get access to the associated DBusGMethodInvocation.
      When claiming the device, remember the sender, and for every
      API entry point, check that the sender is the same as the one
      that made the original claim.
      Trying to enroll a user whilst the device is already claimed
      from another program will fail with:
      ** ERROR **: failed to claim device: Device was already claimed
      This is the first step towards PolicyKit and multi-user support
  6. 16 May, 2008 3 commits
  7. 14 May, 2008 1 commit