1. 19 May, 2019 2 commits
  2. 26 Apr, 2019 2 commits
  3. 25 Apr, 2019 2 commits
  4. 02 Apr, 2019 2 commits
  5. 26 Mar, 2019 2 commits
  6. 15 Mar, 2019 2 commits
  7. 14 Mar, 2019 1 commit
  8. 12 Mar, 2019 2 commits
    • Emmanuele Bassi's avatar
      Port the JS authority to mozjs-60 · dd00683e
      Emmanuele Bassi authored
      API changes in mozjs that need to be reflected in the JS authority:
      
       - the JS::CompileOptions constructor and the JS::CompartmentOptions
         do not allow setting a JS version any more
      
       - do not use NULL comparisons for C++ objects
      
       - the resize() method for a vector has a return value that needs
         to be handled
      
       - JSClassOps has different fields
      dd00683e
    • Emmanuele Bassi's avatar
      Depend on mozjs-60 · c9cd7024
      Emmanuele Bassi authored
      This is the new ESR version of the Mozilla JS engine, superceding
      mozjs-52.
      c9cd7024
  9. 05 Feb, 2019 2 commits
    • Jan Rybar's avatar
      Merge branch 'allow-unset-process-uid' into 'master' · dbf58d4e
      Jan Rybar authored
      Allow uid of -1 for a PolkitUnixProcess
      
      See merge request !17
      dbf58d4e
    • Matthew Leeds's avatar
      Allow uid of -1 for a PolkitUnixProcess · c05472b8
      Matthew Leeds authored
      Commit 2cb40c4d changed PolkitUnixUser, PolkitUnixGroup, and
      PolkitUnixProcess to allow negative values for their uid/gid properties,
      since these are values above INT_MAX which wrap around but are still
      valid, with the exception of -1 which is not valid. However,
      PolkitUnixProcess allows a uid of -1 to be passed to
      polkit_unix_process_new_for_owner() which means polkit is expected to
      figure out the uid on its own (this happens in the _constructed
      function). So this commit removes the check in
      polkit_unix_process_set_property() so that new_for_owner() can be used
      as documented without producing a critical error message.
      
      This does not affect the protection against CVE-2018-19788 which is
      based on creating a user with a UID up to but not including 4294967295
      (-1).
      c05472b8
  10. 08 Jan, 2019 2 commits
  11. 06 Dec, 2018 1 commit
  12. 04 Dec, 2018 2 commits
    • Zbigniew Jędrzejewski-Szmek's avatar
      b534a107
    • Zbigniew Jędrzejewski-Szmek's avatar
      Allow negative uids/gids in PolkitUnixUser and Group objects · 2cb40c4d
      Zbigniew Jędrzejewski-Szmek authored
      (uid_t) -1 is still used as placeholder to mean "unset". This is OK, since
      there should be no users with such number, see
      https://systemd.io/UIDS-GIDS#special-linux-uids.
      
      (uid_t) -1 is used as the default value in class initialization.
      
      When a user or group above INT32_MAX is created, the numeric uid or
      gid wraps around to negative when the value is assigned to gint, and
      polkit gets confused. Let's accept such gids, except for -1.
      
      A nicer fix would be to change the underlying type to e.g. uint32 to
      not have negative values. But this cannot be done without breaking the
      API, so likely new functions will have to be added (a
      polkit_unix_user_new variant that takes a unsigned, and the same for
      _group_new, _set_uid, _get_uid, _set_gid, _get_gid, etc.). This will
      require a bigger patch.
      
      Fixes #74.
      2cb40c4d
  13. 03 Dec, 2018 1 commit
  14. 02 Dec, 2018 1 commit
  15. 30 Nov, 2018 1 commit
  16. 29 Nov, 2018 1 commit
  17. 06 Nov, 2018 5 commits
  18. 25 Sep, 2018 1 commit
  19. 12 Sep, 2018 3 commits
  20. 23 Aug, 2018 4 commits
  21. 16 Aug, 2018 1 commit