From: John Wood <john.wood@gmx.com>
To: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>,
"Andi Kleen" <ak@linux.intel.com>
Cc: John Wood <john.wood@gmx.com>,
kernelnewbies@kernelnewbies.org,
Kees Cook <keescook@chromium.org>,
kernel-hardening@lists.openwall.com
Subject: Re: Notify special task kill using wait* functions
Date: Sun, 11 Apr 2021 10:46:02 +0200 [thread overview]
Message-ID: <20210411084602.GA3111@ubuntu> (raw)
In-Reply-To: <109781.1618010900@turing-police>
Hi,
On Fri, Apr 09, 2021 at 07:28:20PM -0400, Valdis Klētnieks wrote:
> On Fri, 09 Apr 2021 08:06:21 -0700, Andi Kleen said:
>
> > Thinking more about it what I wrote above wasn't quite right. The cache
> > would only need to be as big as the number of attackable services/suid
> > binaries. Presumably on many production systems that's rather small,
> > so a cache (which wouldn't actually be a cache, but a complete database)
> > might actually work.
>
> You also need to consider non-suid things called by suid things that don't
> sanitize input sufficiently before invocation...
>
> Thinking about at - is it really a good thing to try to do this in kernelspace?
> Or is 'echo 1 > /proc/sys/kernel/print-fatal-signals' and a program to watch
> the dmesg and take action more appropriate? A userspace monitor would
> have more options (though a slightly higher risk of race conditions).
>
Thanks for the ideas. I need some time to send a formal proposal that
works properly. I would like to get feedback at that moment. I think it
would be better to discuss about the real patch.
Again, thanks.
John Wood
prev parent reply other threads:[~2021-04-11 8:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210330173459.GA3163@ubuntu>
[not found] ` <79804.1617129638@turing-police>
[not found] ` <20210402124932.GA3012@ubuntu>
[not found] ` <106842.1617421818@turing-police>
[not found] ` <20210403070226.GA3002@ubuntu>
[not found] ` <145687.1617485641@turing-police>
[not found] ` <20210404094837.GA3263@ubuntu>
[not found] ` <193167.1617570625@turing-police>
[not found] ` <20210405073147.GA3053@ubuntu>
[not found] ` <115437.1617753336@turing-police>
2021-04-07 17:51 ` Notify special task kill using wait* functions John Wood
2021-04-07 20:38 ` Valdis Klētnieks
2021-04-08 1:51 ` Andi Kleen
2021-04-09 14:29 ` John Wood
2021-04-09 15:06 ` Andi Kleen
2021-04-09 16:08 ` John Wood
2021-04-09 23:28 ` Valdis Klētnieks
2021-04-11 8:46 ` John Wood [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=20210411084602.GA3111@ubuntu \
--to=john.wood@gmx.com \
--cc=ak@linux.intel.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=valdis.kletnieks@vt.edu \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).