linux-kernel - Re: What's in hid.git for 2.6.30

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200905011809.19971.oliver@neukum.org>
Date:	Fri, 1 May 2009 18:09:19 +0200
From:	Oliver Neukum <oliver@...kum.org>
To:	Jiri Kosina <jkosina@...e.cz>
Cc:	Guillaume Chazarain <guichaz@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: What's in hid.git for 2.6.30

Am Friday 01 May 2009 17:54:39 schrieben Sie:
> On Fri, 1 May 2009, Oliver Neukum wrote:
> > > > > +       if (!(hid->claimed & HID_CLAIMED_INPUT))
> > > > > +               return 0;
> > > > > +
> > > >
> > > > is there a guarantee all keyboards will be claimed as input devices?
> > >
> > > do you see any way how hid->inputs could currently be initialized other
> > > than the device being claimed by hid-input?
> >
> > No, but I am worried about a false return of 0 here, not the other way
> > round. This method is necessary because keyboards don't wake up
> > if a key is released. Suspending a keyboard with a key pressed will lead
> > to an endless repetition of that key.
> > So I wonder whether it is possible to have a keyboard not claimed as an
> > input device.
>
> If driven by usbhid, the only way how keyboard could be handled if not
> claimed by hid-input is a userspace hiddev or hidraw driver. And we don't
> suspend if hidraw/hiddev node is open, right?

What happens if the node is closed? Will hid forget that a key had
been pressed? I must admit that I can't tell where in hid the key repetition
logic is located.

	Regards
		Oliver

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/