linux-kernel - Re: [PATCH 2/2] vt: defkeymap: Map keycodes above 127 to K

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] [day] [month] [year] [list]

Message-ID: <1755f4ab-f0c4-4442-8446-ae7b104b4e89@kernel.org>
Date: Tue, 22 Jul 2025 11:07:41 +0200
From: Jiri Slaby <jirislaby@...nel.org>
To: Myrrh Periwinkle <myrrhperiwinkle@...labs.xyz>,
 Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Arthur Taylor <art@...ed.ca>
Cc: Greg Kroah-Hartman <gregkh@...e.de>, linux-kernel@...r.kernel.org,
 linux-serial@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH 2/2] vt: defkeymap: Map keycodes above 127 to K_HOLE

On 02. 07. 25, 16:17, Myrrh Periwinkle wrote:
> The maximum number of keycodes got bumped to 256 a very long time ago,
> but the default keymaps were never adjusted to match. This is causing
> the kernel to interpret keycodes above 127 as U+0000 if the shipped
> generated keymap is used.
> 
> Fix this by mapping all keycodes above 127 to K_HOLE so the kernel
> ignores them.
> 
> The contents of this patche were generated by rerunning `loadkeys
> --mktable --unicode` and only including the changes to map keycodes
> above 127 to K_HOLE.

OK., makes sense.

Reviewed-by: Jiri Slaby <jirislaby@...nel.org>


> Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
> Signed-off-by: Myrrh Periwinkle <myrrhperiwinkle@...labs.xyz>
> Cc: stable@...r.kernel.org


-- 
js
suse labs