From: Kees Cook <keescook@chromium.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Jiri Slaby <jirislaby@kernel.org>,
Simon Brand <simon.brand@postadigitale.de>,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH v3 0/2] tty: Allow TIOCSTI to be disabled
Date: Tue, 1 Nov 2022 19:46:51 -0700 [thread overview]
Message-ID: <202211011946.F7B4C690@keescook> (raw)
In-Reply-To: <Y2HWJUuir8E33GkP@kroah.com>
On Wed, Nov 02, 2022 at 03:29:57AM +0100, Greg Kroah-Hartman wrote:
> On Tue, Nov 01, 2022 at 07:15:43PM -0700, Kees Cook wrote:
> > On Sat, Oct 22, 2022 at 11:29:47AM -0700, Kees Cook wrote:
> > > This is so very long over-due. We just need to do this and put an end
> > > to this legacy operation.
> >
> > thread ping. Should I carry this in my hardening tree instead?
>
> I can take it in my tree, I have a bunch of tty/serial patches to go
> through this week, give me a few more days please.
Sounds good; thanks for the update!
--
Kees Cook
prev parent reply other threads:[~2022-11-02 2:46 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
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 [this message]
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=202211011946.F7B4C690@keescook \
--to=keescook@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox