touch-packages team mailing list archive

[Jamie Strandboge <jamie@xxxxxxxxxx>]

I am going to mark this as "incomplete". Antii says "Currently the
pinlock dialog is implemented as snapdecision and thus any application
that is allowed to use the notifications can potentially trick the user
to provide his PIN code or Passcode to the application by invoking the
pinlock dialog." However, AppArmor policy explicitly disables the
snapdecisions interface and there is no code or described methodology
describing the problem so I can't determine if this is mere concern that
there might be a problem or that there is an actual problem.

** Changed in: unity-notifications
       Status: Triaged => Incomplete

** Changed in: unity8 (Ubuntu)
       Status: Triaged => Incomplete

** Changed in: unity8 (Ubuntu)
   Importance: Medium => High

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

Title:
  pinlock snap decision potentially allows malicious app to gain access
  to user PIN and Passcode

Status in Server and client library for desktop notifications in Unity:
  Incomplete
Status in “unity8” package in Ubuntu:
  Incomplete

Bug description:
  Currently the pinlock dialog is implemented as snapdecision and thus
  any application that is allowed to use the notifications can
  potentially trick the user to provide his PIN code or Passcode to the
  application by invoking the pinlock dialog.

  As we want to allow applications to send normal notifications and
  snapdecisions we can't just block the whole notify service from them,
  but also we don't have any means to block just one of them.

  Thus the only solution is to remove the pinlock from snap decisions
  completely and implement a standalone dbus service for pinlock dialog
  which can be properly confined.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-notifications/+bug/1306769/+subscriptions