[Differential] [Commented On] D1672: Add support for touch events in fakeinput protocol and interface.

[graesslin (Martin Gräßlin)]

graesslin added a comment.


  In https://phabricator.kde.org/D1672#31094, @bshah wrote:
  
  > In https://phabricator.kde.org/D1672#31046, @graesslin wrote:
  >
  > > I'm wondering: should we ensure that the ids are correct. E.g. a touchUp for id 1 doesn't make sense if we never got a touchDown for id 1. This would require tracking the used ids in FakeInputInterface. But it must be done somewhere - either in the library or by the user of the library.
  >
  >
  > IMO client ideally will not send bogus event. And in any case if it does, compositor itself should ignore bogus events because it is the one which is processing in end..
  
  
  a client could also use this to attack (crash) the Compositor by sending bogus events. That's security relevant from my point of view.

REPOSITORY
  rKWAYLAND KWayland

REVISION DETAIL
  https://phabricator.kde.org/D1672

EMAIL PREFERENCES
  https://phabricator.kde.org/settings/panel/emailpreferences/

To: bdhruve, graesslin, Plasma, bshah
Cc: bshah, graesslin, plasma-devel, sebas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20160525/6f95be7f/attachment-0001.html>