[Bug 833945] Re: Allow to install system wide license keys

[Anthony Lenton]

Discussed briefly on irc.

One way to make this call secure would be to make the AddLicenseKey call:
AddLicenseKey(packagename, token, server)

aptdaemon could then contact the (trusted) server, authenticate with the
provided token and retrieve the license key itself.

It would need to receive the OAuth token as an argument because it
doesn't have access to the session bus to request the token itself.

The server argument would need to be restricted to "production" or
"staging", so that you can't ask aptdaemon to contact just any server.

It might be best to package the sca client library separately for
aptdaemon to use.

Optionally, aptdaemon could read an environment variable to check which
server it should contact, and make the call receive only
packagename+token.

It could even reuse SOFTWARE_CENTER_BUY_HOST, the same env var software-
center uses, with the same restrictions: it should only be allowed to
refer to the trusted staging or production server.

Alternatively to the packagename, the call could receive a subscription
(numeric) id, and fetching that from the sca api will provide the
package name together with the license key.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to aptdaemon in Ubuntu.
https://bugs.launchpad.net/bugs/833945

Title:
  Allow to install system wide license keys

Status in Online service used by software center:
  New
Status in “aptdaemon” package in Ubuntu:
  In Progress

Bug description:
  There is the need to allow sharing software license key by all users
  on the system. So they need to be dropped to an accessible location on
  the system. This bug tracks the discussion and progress of this
  effort.

  From a security point of view we allow a desktop user to "randomly"
  drop files on the system. So we should try to define the dropping area
  and the content of the file as tight as possible.

  Open issues:
  * Can we assume that we can patch or force the shipped software in /opt to use a common place defined by our policy (problem with proprietary software)?
  * If the above question is yes: Can we store the licenses in a central repository e.g. /var/licenses/pkgname.key? Or should we store them in the corresponding /opt/pkgname dir?
  * If the first question is no: Can we still assume that the key has to be stored in the /opt/pkgname dir? E.g. Does a "special" customer insist on uppercase naming which is not allowed as a package name /opt/AcrobatReader?
  * Can we sign the key by Launchpad to make sure to only drop a file which can be sure of to be license key? The signature check needs to be done by aptdaemon
  * We need a trusted way to transfer the location of the key to aptdaemon - current solution would be to store the key path in a package control field (XB-LicenseKeyPath). But we could also append this information to a signed license key, see question above.

To manage notifications about this bug go to:
https://bugs.launchpad.net/software-center-agent/+bug/833945/+subscriptions