From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: David Laight <David.Laight@ACULAB.COM>
Cc: Kees Cook <keescook@chromium.org>, Kees Cook <kees@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
Simon Brand <simon.brand@postadigitale.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-hardening@vger.kernel.org"
<linux-hardening@vger.kernel.org>,
"Dave@mielke.cc" <Dave@mielke.cc>
Subject: Re: [PATCH v3 2/2] tty: Allow TIOCSTI to be disabled
Date: Thu, 29 Jun 2023 15:32:19 +0200 [thread overview]
Message-ID: <20230629133219.5z667lt6pz25exkf@begin> (raw)
In-Reply-To: <55c209a024a94d1f9c6af85dfddb11a0@AcuMS.aculab.com>
David Laight, le jeu. 29 juin 2023 13:23:54 +0000, a ecrit:
> From: Samuel Thibault
> > Sent: 28 June 2023 07:07
> ...
> > > So is there really no solution for brltty and TIOCSTI being disabled?
> >
> > No, there is no way to simulate characters on the Linux console. The
> > alternative would be to use uinput, but that simulates keycodes, not
> > characters, thus requiring backtranslating first, which is very fragile.
>
> It could probably be rewritten to use a pseudo-tty pair.
That's what yasr does for instance, but that does not make the login
prompt accessible, which is a must (just like sighted users don't log in
blindly...)
Samuel
next prev parent reply other threads:[~2023-06-29 13:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-22 18:29 [PATCH v3 0/2] tty: Allow TIOCSTI to be disabled Kees Cook
2022-10-22 18:29 ` [PATCH v3 1/2] tty: Move sysctl setup into "core" tty logic Kees Cook
2022-10-22 18:29 ` [PATCH v3 2/2] tty: Allow TIOCSTI to be disabled Kees Cook
2022-11-15 13:17 ` Geert Uytterhoeven
2022-12-27 23:40 ` Samuel Thibault
2022-12-27 23:41 ` Samuel Thibault
2022-12-28 3:32 ` Kees Cook
2022-12-28 20:57 ` Samuel Thibault
2023-06-25 15:56 ` Samuel Thibault
2023-06-27 21:50 ` Samuel Thibault
2023-06-28 0:21 ` Paul Moore
2023-06-28 2:48 ` Kees Cook
2023-06-28 6:07 ` Samuel Thibault
2023-06-28 16:32 ` Kees Cook
2023-07-02 0:00 ` Samuel Thibault
2023-07-03 19:41 ` Kees Cook
2023-06-29 13:23 ` David Laight
2023-06-29 13:32 ` Samuel Thibault [this message]
2022-11-02 2:15 ` [PATCH v3 0/2] " Kees Cook
2022-11-02 2:29 ` Greg Kroah-Hartman
2022-11-02 2:46 ` Kees Cook
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=20230629133219.5z667lt6pz25exkf@begin \
--to=samuel.thibault@ens-lyon.org \
--cc=Dave@mielke.cc \
--cc=David.Laight@ACULAB.COM \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=kees@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=simon.brand@postadigitale.de \
/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.