Public bug reported:
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.
** Affects: unity-scopes-api (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-api in
Ubuntu.
https://bugs.launchpad.net/bugs/1554040
Title:
Allow hiding authentication data in scope binary
Status in unity-scopes-api package in Ubuntu:
New
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/ubuntu/+source/unity-scopes-api/+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
