1. 22 May, 2008 8 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.
      46a9783b
    • 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.
      61a2266e
    • 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.
      5e194488
    • 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.
      8529a43b
    • 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.
      b1b5e2b4
    • Bastien Nocera's avatar
      Kill LoadPrintDataFromStorage · 5d4e23ab
      Bastien Nocera authored
      First FromStorage variant to go
      5d4e23ab
    • 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.
      7f592dd2
    • 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.
      c63f624a
  2. 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
      1748e5f4
  3. 14 May, 2008 1 commit
  4. 06 Apr, 2008 1 commit
  5. 06 Mar, 2008 2 commits
  6. 05 Mar, 2008 1 commit