Ok, a bit more info, copying from https://bugzilla.gnome.org/show_bug.cgi?id=771547#c62
-- The internal Google OAuth2 authentication had been introduced in eds 3.20.0 (thus it's pretty new), for which I released eds 3.20.6 with all the yet-known fixes recently, in a hope that distros which still use 3.20.x will update and thus will help all users. I'm not going to change the Google API keys in eds, because the statistics which the Google server provides indicate that the usage is pretty fine with the internal eds Google API keys. Just compare, the numbers from the Tuesday this week: - for the GOA, the past 24 hours: CalDAV API - 104 millions of requests, 99 millions errors (95.34%) Tasks API - 65 millions of requests, 65 millions errors (99.93%) - for the eds, the past 24 hours: CalDAV API - 399 thousands of requests, 5 thousands errors (1.37%) CardDAV API - 59 thousands of requests, 12 errors (0.02%) Contacts API - 30 thousands of requests, 31 errors (0.1%) Tasks API - 9 thousands of requests, 0 errors (0%) ** Bug watch added: GNOME Bug Tracker #771547 https://bugzilla.gnome.org/show_bug.cgi?id=771547 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1650007 Title: Consider changing Google API key Status in account-plugins package in Ubuntu: New Bug description: evolution-data-server (e-d-s) 3.20 before 3.20.6 and 3.22 before 3.22.2 had bugs that caused users using Google services to experience daily limit timeouts and authentication errors. Unfortunately, users using older versions are causing those problems for everyone that still uses the affected API key. Therefore GNOME is updating the API key used by GNOME Online Accounts. For more info, see LP: #1649995 and https://bugzilla.gnome.org/774202 - I don't know yet if e-d-s before 3.20 is also affected. I asked but you're welcome to ask the Evolution devs yourself. https://bugzilla.gnome.org/show_bug.cgi?id=771547#c61 - Upstream evolution has two ways to configure a Google account: GNOME Online Accounts and e-d-s. I assume Ubuntu Online Accounts is a 3rd way. (I think e-d-s will need to switch to a new Google API key too but that hasn't happened yet.) - For Ubuntu 16.10, we need the latest evolution-data-server SRU (LP: #1639926) to be pushed to yakkety-updates and fully 100% phased before publishing the new key. - Therefore, assuming Ubuntu Online Accounts is affected, I suggest you consider changing the Google API key used in Ubuntu 16.10 and above. Once we figure out if e-d-s needs to be updated for 16.04 (and possibly earlier releases), I believe we'll need to update the key there too. - On the other hand, since we control Ubuntu updates (unlike GNOME which has not control over who uses what version of their stuff) maybe we don't need to change the key after all. Maybe we just need to push the e-d-s SRUs as security updates to ensure people use the fixed versions? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1650007/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
