linux-kernel - Re: Re (hello?): [PATCH] Let keyboard notifiers modify key codes

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]

Date:	Fri, 9 Jan 2009 22:01:44 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Samuel Thibault <samuel.thibault@...-lyon.org>
Cc:	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
	dmitry.torokhov@...il.com, linux-input@...r.kernel.org
Subject: Re: Re (hello?): [PATCH] Let keyboard notifiers modify key codes

> > Surely that is just a new keymap ?
> 
> No. That would mean a lot of keymapSSS. Doing it the keymap way

Why - its an  algorithmic question about how to edit them - remember you
can edit keymaps in programs at runtime and live.

> This really is a problem that is orthogonal to keymaps: I'm here talking
> about _physical_ keys remapping, not remapping what is printed on them
> (which is done after that).

Ok so this is analogous to the X key remapping. In which case a notifier
seems as sane as any other way to perform the action if you want it to be
an add on loadable feature.
--
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/