Use new API keys
Bug #1064293 reported by
Alberto Mardegan
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Online Accounts: Account plugins |
Fix Released
|
Critical
|
Alberto Mardegan | ||
account-plugins (Ubuntu) |
Fix Released
|
Critical
|
Unassigned |
Bug Description
Most of the API keys currently used in the project have been registered under mine or somebody else's personal account.
We should get some keys registered by Canonical, and use them.
Related branches
lp:~mardy/account-plugins/new-keys
- Ken VanDine: Approve
- jenkins (community): Needs Fixing (continuous-integration)
-
Diff: 75 lines (+4/-41)1 file modifiedsrc/google.vala (+4/-41)
Changed in online-accounts-account-plugins: | |
assignee: | nobody → Alberto Mardegan (mardy) |
importance: | Undecided → Critical |
status: | New → In Progress |
Changed in online-accounts-account-plugins: | |
status: | In Progress → Fix Released |
Changed in online-accounts-account-plugins: | |
milestone: | none → 0.9 |
Changed in account-plugins (Ubuntu): | |
importance: | Undecided → Critical |
milestone: | none → ubuntu-12.10 |
To post a comment you must log in.
I marked this bug as affecting the Ubuntu package as well, because we could continue use the current keys in the upstream package (which might be used by other distros as well) and specify the new keys only while building the Ubuntu package.