From: Anssi Hannula <anssi.hannula@gmail.com>
To: Dmitry Torokhov <dtor@insightbb.com>
Cc: linux-input@atrey.karlin.mff.cuni.cz, linux-kernel@vger.kernel.org
Subject: input/eventX permissions, force feedback
Date: Tue, 18 Jul 2006 12:42:49 +0300 [thread overview]
Message-ID: <44BCAD19.8070004@gmail.com> (raw)
Currently most distributions have /dev/input/event* strictly as 0600
root:root or 0640 root:root. The user logged in will not have rights to
the device, unlike /dev/input/js*, as he could read all passwords from
the keyboard device.
This is a problem, because /dev/input/event* is used for force feedback
and should therefore be user-accessible.
I can think of the following solutions to this problem:
1. Some creative udev rule to chmod /dev/input/event* less strictly when
it has a /dev/input/js* and is thus a gaming device.
2. Some creative udev rule to chmod /dev/input/event* more strictly when
it is a keyboard.
3. Have another force feedback interface also in /dev/input/js*.
I prefer the first one, do you think it is a good solution or do you
have a better one?
If I go with the first one, what is the preferred way of finding out a
gaming device in udev rule?
--
Anssi Hannula
next reply other threads:[~2006-07-18 9:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-18 9:42 Anssi Hannula [this message]
2006-07-18 12:20 ` input/eventX permissions, force feedback Dmitry Torokhov
2006-07-18 14:02 ` Anssi Hannula
2006-07-18 14:14 ` Dmitry Torokhov
2006-07-18 14:31 ` Anssi Hannula
2006-07-18 16:50 ` Andrey Borzenkov
2006-07-18 17:07 ` Anssi Hannula
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44BCAD19.8070004@gmail.com \
--to=anssi.hannula@gmail.com \
--cc=dtor@insightbb.com \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox