wminput should provide udev rule

Bug #140890 reported by Justin Dugger
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
cwiid (Ubuntu)
Invalid
Undecided
Luke Yelavich
udev (Ubuntu)
Won't Fix
Wishlist
Unassigned

Bug Description

wminput, when installed, requires a uinput device set via udev rules as described in the manpage. It should be trivial to write a 40-wminput.rules file to add for this to work out of box.

Revision history for this message
Justin Dugger (jldugger) wrote :

This patch should add a rule as outlined in the manpage.

Luke Yelavich (themuso)
Changed in cwiid:
assignee: nobody → themuso
status: New → In Progress
Revision history for this message
Justin Dugger (jldugger) wrote :

Apparently this is something better handled by the udev package itself, in which case, something smarter may be needed than the above rule.

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

Please justify why uinput can be world-readable and writable; what does the device do? What are the security implications?

Changed in udev:
importance: Undecided → Wishlist
status: New → Incomplete
Revision history for this message
Justin Dugger (jldugger) wrote :

From the kernel uinput.c:
* User level driver support for input subsystem

wminput is used to make the mouse cursor controllable by a Wiimote connected via bluetooth. The security implications are unclear to me. I happen to know that the device is also used for thinkfinger, which will be pulled in via Debian upstream soon. Would it be more appropriate to create a new user group akin to the fuse module group? If not, I'm afraid the packaged README suggests two insecure approaches likely to be used by anyone installing this package, as it's required.

Revision history for this message
Justin Dugger (jldugger) wrote :

After speaking with cjwatson on this, I think it may be simpler and wiser to advise users to run wminput via sudo. Newer versions in upstream have a better approach that alter related functionality anyways.

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

This implies to me that any user could insert input events to your X server, and thus click on any part of the screen, etc.

These permissions are definitely inappropriate.

Changed in udev:
status: Incomplete → Won't Fix
Revision history for this message
Justin Dugger (jldugger) wrote :

If you're having permission problems with wminput, run with sudo. The README's solution is insecure and future work appears to take a much smarter approach.

Changed in cwiid:
status: In Progress → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.