This bug was fixed in the package unity-scopes-api -
1.0.4+16.04.20160402.4-0ubuntu1
---------------
unity-scopes-api (1.0.4+16.04.20160402.4-0ubuntu1) xenial; urgency=medium
[ Marcus Tomlinson ]
* Simplify debian/control munging. Look for clang-format as opposed to
clang-format-3.x. Added missing initializations to TypedScopeFixture
(Bug #1542906). Allow clients to specify authentication parameters
(Bug #1554040). (LP: #1554040, #1542906)
[ Michi Henning ]
* Fixed incorrect generation of Replaces: and Conflicts: entries in
debian/control for xenial. Fixed incorrect library soname for vivid.
-- Marcus Tomlinson <marcus.tomlin...@canonical.com> Sat, 02 Apr 2016
03:24:17 +0000
** Changed in: unity-scopes-api (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-shell in
Ubuntu.
https://bugs.launchpad.net/bugs/1554040
Title:
Allow hiding authentication data in scope binary
Status in Canonical System Image:
Fix Committed
Status in unity-scopes-api package in Ubuntu:
Fix Released
Status in unity-scopes-shell package in Ubuntu:
In Progress
Bug description:
The current scope API doesn't allow the developer to specify the OAuth client
keys at runtime, they must reside in the .service files which end up installed
on the filesystem.
Some people are concerned about exposing their API keys, and would rather
embed them in their scope binary and specify them at runtime. While
acknowledging that this will actually not improve the security, this
possibility is offered by all other Online Accounts APIs, and it would be nice
if scopes offered this too.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1554040/+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
