it's 3.31.3 release day, upload a tarball and show that our software is more stable than this table 彡┻━┻

  1. 02 Dec, 2018 1 commit
  2. 31 Oct, 2018 1 commit
  3. 27 Oct, 2018 1 commit
  4. 10 Oct, 2018 1 commit
  5. 05 Oct, 2018 1 commit
    • Jacob Keller's avatar
      pam: lookup XDG_RUNTIME_DIR using get_any_env · b22d058a
      Jacob Keller authored
      The pam_gnome_keyring.so PAM module needs to find the daemon control
      file, which is stored in $XDG_RUNTIME_DIR/keyring/control.
      Unfortunately when commit 2ca51a0a ("daemon: Stop exporting the
      $GNOME_KEYRING_CONTROL env variable", 2014-03-06) switched to using
      XDG_RUNTIME_DIR preferentially over GNOME_KEYRING_CONTROL, it was looked
      up using getenv().
      
      Unfortunately XDG_RUNTIME_DIR isn't always set in the environment, but
      may need to be looked up from pam_getenv. Indeed, the function
      get_any_env already exists for this purpose.
      
      Because of the incorrect environment lookup, lookup_daemon will
      incorrectly report that the gnome-keyring-daemon is not running, even
      though it is. This results in starting the daemon multiple times, and
      potentially failing to shut it down, or start it correctly when changing
      the password.
      
      To fix this, move the code for determining the control file path from
      gkr-pam-client.c into gkr-pam-module.c This will using get_any_env(),
      and avoids the need for passing the pam_handle_t variable into
      gkr-pam-client.c
      
      It does mean that the control variable must be allocated with space,
      since we need to combine the environment value with a different suffix
      depending on if we use GNOME_KEYRING_CONTROL or XDG_RUNTIME_DIR.
      
      Add a function get_control_file, so that the logic for determining the
      control file path remains in one location.
      Signed-off-by: Jacob Keller's avatarJacob Keller <jacob.keller@gmail.com>
      b22d058a
  6. 28 Aug, 2018 1 commit
  7. 27 Aug, 2018 1 commit
  8. 16 Aug, 2018 1 commit
  9. 24 Jul, 2018 2 commits
  10. 18 Jul, 2018 1 commit
  11. 14 Jul, 2018 1 commit
  12. 12 Jun, 2018 3 commits
  13. 25 May, 2018 2 commits
  14. 13 May, 2018 1 commit
  15. 07 May, 2018 3 commits
  16. 18 Apr, 2018 1 commit
  17. 27 Mar, 2018 1 commit
  18. 24 Mar, 2018 1 commit
  19. 23 Mar, 2018 1 commit
  20. 20 Mar, 2018 3 commits
  21. 19 Mar, 2018 5 commits
  22. 13 Mar, 2018 2 commits
  23. 12 Mar, 2018 1 commit
  24. 05 Mar, 2018 2 commits
  25. 04 Mar, 2018 2 commits