From: Kees Cook <keescook@chromium.org>
To: Simon Brand <simon.brand@postadigitale.de>
Cc: linux-hardening@vger.kernel.org
Subject: Re: Reconsider possibility to disable icotl TIOCSTI
Date: Fri, 14 Oct 2022 21:37:04 -0700 [thread overview]
Message-ID: <202210142135.252DFDF3C8@keescook> (raw)
In-Reply-To: <Y0m9l52AKmw6Yxi1@hostpad>
On Fri, Oct 14, 2022 at 07:51:11PM +0000, Simon Brand wrote:
> please reconsider to add a possibility to disable icotl TIOCSTI.
Yeah, please, let's. I always wanted to, and its use case is very
narrow. Even OpenBSD has removed it, somewhat motivated by the attempt
to remove it from Linux in 2017. I've sent this now:
https://lore.kernel.org/linux-hardening/20221015041626.1467372-2-keescook@chromium.org/
--
Kees Cook
next prev parent reply other threads:[~2022-10-15 4:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 19:51 Reconsider possibility to disable icotl TIOCSTI Simon Brand
2022-10-15 4:37 ` Kees Cook [this message]
2022-10-15 5:42 ` Greg KH
2022-10-15 6:45 ` 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=202210142135.252DFDF3C8@keescook \
--to=keescook@chromium.org \
--cc=linux-hardening@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox