1. 08 Jun, 2017 1 commit
  2. 08 Feb, 2017 1 commit
  3. 22 Dec, 2016 1 commit
  4. 14 Dec, 2016 1 commit
  5. 11 Nov, 2015 1 commit
  6. 16 Sep, 2015 1 commit
  7. 15 Sep, 2015 1 commit
  8. 14 Sep, 2015 1 commit
  9. 11 Sep, 2015 1 commit
  10. 05 Aug, 2015 1 commit
  11. 22 May, 2015 1 commit
    • Ray Strode's avatar
      identity: Separate identity service off into its own process · ac7047d8
      Ray Strode authored
      This commit segregates the kerberos specific functionality off
      into its own helper process.
      
      This has a couple of benefits:
      
      1) It is actually a better fit for how the code was initially designed,
      which was first staged in gnome-settings-daemon with g-o-a talking to
      it. Right now we have gnome-online-accounts talking to itself,
      in-process, through d-bus, which is suboptimal.
      
      2) It keeps any leaks or crashes in the kerberos code from bringing
      down the whole online accounts daemon.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=739593
      ac7047d8
  12. 04 May, 2015 1 commit
  13. 26 Mar, 2015 1 commit
  14. 04 Mar, 2015 1 commit
  15. 24 Feb, 2015 1 commit
    • Debarshi Ray's avatar
      Remove Yahoo! support · 64cfb818
      Debarshi Ray authored
      It does not work. There are currently no known applications that use
      it. Keeping the code means that some distributions enable it, only to
      have users complain that it does not work.
      
      Will be restored once the situation changes.
      
      See: https://bugzilla.gnome.org/721061
      64cfb818
  16. 18 Dec, 2014 1 commit
  17. 30 Sep, 2014 1 commit
    • Debarshi Ray's avatar
      Support locked accounts · 2e6a2c9c
      Debarshi Ray authored
      Locked accounts are those that have been pre-configured by the system
      administrator. Users are discouraged from removing these, which is why
      org.gnome.OnlineAccounts.Account.Remove will refuse to do so. One can
      work around this by manually editing accounts.conf.
      
      Fixes: https://bugzilla.gnome.org/737656
      2e6a2c9c
  18. 05 Jun, 2014 2 commits
  19. 19 May, 2014 1 commit
  20. 25 Mar, 2014 1 commit
    • Debarshi Ray's avatar
      Remove the author field from file headers · 01fddbfb
      Debarshi Ray authored
      The information was often stale and we did not consistently have it in
      all the files. Git is a much more reliable source for this kind of
      information. Unlike the copyright notice, the author field has no legal
      significance, so it was just unnecessary baggage.
      01fddbfb
  21. 05 Mar, 2014 1 commit
  22. 03 Feb, 2014 3 commits
  23. 29 Jan, 2014 1 commit
  24. 13 Jan, 2014 1 commit
  25. 18 Jun, 2013 1 commit
  26. 12 Jun, 2013 1 commit
  27. 10 Jun, 2013 1 commit
  28. 05 Mar, 2013 1 commit
    • Debarshi Ray's avatar
      daemon: Do not use notifications when an account needs attention · 8750cf18
      Debarshi Ray authored
      We want the applications to handle the notification themselves if the
      credentials for an account do not work (ie., if EnsureCredentials
      fails). Having the daemon throw a notification is bad because:
        * it does not give the user sufficient context to determine what
          actually failed
        * background services might be calling EnsureCredentials, and these
          should never lead to a notification unless it was in response to
          an explicit user action
      
      This also reverts commit cbcb0da9.
      
      Fixes: https://bugzilla.gnome.org/660882
      8750cf18
  29. 04 Mar, 2013 1 commit
  30. 01 Mar, 2013 1 commit
  31. 14 Feb, 2013 3 commits
  32. 05 Feb, 2013 1 commit
    • Debarshi Ray's avatar
      Guard against invalid SSL certificates · edde7c63
      Debarshi Ray authored
      None of the branded providers (eg., Google, Facebook and Windows Live)
      should ever have an invalid certificate. So set "ssl-strict" on the
      SoupSession object being used by GoaWebView.
      
      Providers like ownCloud and Exchange might have to deal with
      certificates that are not up to the mark. eg., self-signed
      certificates. For those, show a warning when the account is being
      created, and only proceed if the user decides to ignore it. In any
      case, save the status of the certificate that was used to create the
      account. So an account created with a valid certificate will never
      work with an invalid one, and one created with an invalid certificate
      will not throw any further warnings.
      
      Fixes: CVE-2013-0240
      edde7c63
  33. 29 Jan, 2013 1 commit
  34. 18 Dec, 2012 2 commits