All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Herrmann <dh.herrmann@gmail.com>
To: Nestor Lopez Casado <nlopezcasad@logitech.com>
Cc: Jiri Kosina <jkosina@suse.cz>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	"open list:HID CORE LAYER" <linux-input@vger.kernel.org>,
	Olivier Gay <ogay@logitech.com>,
	Benjamin Tissoires <benjamin.tissoires@gmail.com>,
	Mathieu Meisser <mmeisser@logitech.com>
Subject: Re: HID vendor access from user space
Date: Tue, 15 Apr 2014 04:16:11 +0200	[thread overview]
Message-ID: <CANq1E4Q=DC6OvtvgBtqDoYb4ZWVWSf9KXBo3=4jwS-AWzFhCiw@mail.gmail.com> (raw)
In-Reply-To: <CAE7qMro259DVdPqDw4CN1hNp8kQ933F6f6ZMa7BPCOXuNWTQ8Q@mail.gmail.com>

Hi

On Mon, Apr 14, 2014 at 12:00 PM, Nestor Lopez Casado
<nlopezcasad@logitech.com> wrote:
> David, Jiri,
>
> After considering our discussion here, which is your position on
> extending the hidraw nodes to include separate nodes for top level
> vendor collections ?

Patches, patches, patches!

I am currently on the road, but it's always easier to see real code
than just the theory. I have no real objections to provide multiple
hidraw interfaces. However, I think that doesn't solve your problem.
For instance, you still need to set proper access-rights on the hidraw
node. However, some other devices might export unsafe interfaces via
vendor-extensions, and you don't wanna make those hidraw nodes
user-accessible. Therefore, you still need a udev-rule to match on
Logitech-stuff. You could do that as a small Logitech-driver in the
kernel. But ok, I'm fine with moving those whitelists to user-space.

Thanks
David

  reply	other threads:[~2014-04-15  2:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-17 11:47 HID vendor access from user space Nestor Lopez Casado
2013-05-21 13:12 ` David Herrmann
2014-04-02  7:05   ` Nestor Lopez Casado
2014-04-03 13:57     ` Jiri Kosina
2014-04-07 16:15       ` Nestor Lopez Casado
2014-04-07 16:27         ` David Herrmann
2014-04-08 15:53           ` Nestor Lopez Casado
2014-04-14 10:00             ` Nestor Lopez Casado
2014-04-15  2:16               ` David Herrmann [this message]
2014-04-15  7:36                 ` Nestor Lopez Casado
2014-04-15  7:39               ` Jiri Kosina
2014-04-15  8:47                 ` Nestor Lopez Casado
2014-04-16 14:53                   ` Jiri Kosina
2014-04-23  9:14                     ` Nestor Lopez Casado
2014-04-23  9:27                       ` David Herrmann

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='CANq1E4Q=DC6OvtvgBtqDoYb4ZWVWSf9KXBo3=4jwS-AWzFhCiw@mail.gmail.com' \
    --to=dh.herrmann@gmail.com \
    --cc=benjamin.tissoires@gmail.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=jkosina@suse.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=mmeisser@logitech.com \
    --cc=nlopezcasad@logitech.com \
    --cc=ogay@logitech.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.