[Bug 833053] Re: license_key_path should not (yet) support per-user location

[Sebastian Heinlein]

Hello Michael and Michael,

So it makes sense to specify the complete absolute path to the global
key file in the package record.

The main problem is that you don't know how secure the soon to be
deployed software in /opt will be. Aptdaemon checks already if the
license key is an executable or starts with a shebang line. Or if there
are any symlinks in the license key path. Furthermore aptdaemon doesn't
overwrite any existing file.

I cannot imagine any locations that should be restricted by the web ui
generally, since it is completely up to the application developer e.g.
if the conf.d directory is used to store configuration snippets or just
keys.

Can we gurantee that all software installed in /opt will follow the
/opt/pkgname schema? Or will there be some exceptions, e.g.
/opt/AdobeAcroread?

-- 
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/833053

Title:
  license_key_path should not (yet) support per-user location

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

Bug description:
  Currently USC won't allow a second user on a single system to purchase
  an app that is already installed, so we need to ensure that the
  devportal doesn't (yet) allow license_key_path using the home
  directory.

  That said, while I was JDIing that, the current implementation allows
  a license file directly in /opt which seems sub-optimal (ie. potential
  conflicts with other files). After chatting with Anthony, we thought
  that for a system-wide license_key_path, it should be a relative
  pathname - relative to the executable location (ie. within
  /opt/[package_name]/).

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