[Touch-packages] [Bug 1609616] Re: Alarm/AlarmModel should be confined per app

2017-05-31 Thread Jamie Strandboge
** Changed in: apparmor-easyprof-ubuntu (Ubuntu)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu
in Ubuntu.
https://bugs.launchpad.net/bugs/1609616

Title:
  Alarm/AlarmModel should be confined per app

Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Won't Fix

Bug description:
  Currently, when you use the AlarmModel and calendar apparmor policy,
  your app can view, add, edit and delete alarms even those that were
  created by other apps like for example the core clock app.

  I think it would be better if the model only gives your app the permission to 
view, edit and delete alarms created by your app. Then when the alarm is 
triggered, the appropriate app will open and not alwayd the clock app.
  This means that alarms in the AlarmModel can be distinguished by app and bot 
as whole.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor-easyprof-ubuntu/+bug/1609616/+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


[Touch-packages] [Bug 1609616] Re: Alarm/AlarmModel should be confined per app

2016-08-05 Thread Christian Dywan
** Package changed: ubuntu-ui-toolkit (Ubuntu) => apparmor-easyprof-
ubuntu (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu
in Ubuntu.
https://bugs.launchpad.net/bugs/1609616

Title:
  Alarm/AlarmModel should be confined per app

Status in apparmor-easyprof-ubuntu package in Ubuntu:
  New

Bug description:
  Currently, when you use the AlarmModel and calendar apparmor policy,
  your app can view, add, edit and delete alarms even those that were
  created by other apps like for example the core clock app.

  I think it would be better if the model only gives your app the permission to 
view, edit and delete alarms created by your app. Then when the alarm is 
triggered, the appropriate app will open and not alwayd the clock app.
  This means that alarms in the AlarmModel can be distinguished by app and bot 
as whole.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor-easyprof-ubuntu/+bug/1609616/+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