From: Kees Cook <keescook@chromium.org>
To: John Wood <john.wood@gmx.com>
Cc: kernel-hardening@lists.openwall.com
Subject: Re: [RFC PATCH 0/9] Fork brute force attack mitigation (fbfam)
Date: Sun, 6 Sep 2020 13:25:47 -0700 [thread overview]
Message-ID: <202009061323.75C4EC509F@keescook> (raw)
In-Reply-To: <20200906142029.6348-1-john.wood@gmx.com>
On Sun, Sep 06, 2020 at 04:20:20PM +0200, John Wood wrote:
> The goal of this patch serie is to detect and mitigate a fork brute force
> attack.
I look forward to reviewing it on the list! :) In the meantime, you
could try adding this series as a branch on github (or whatever git
host) tree you have access to. That would allow contextual commenting
there too, if email continues to be a blocker.
--
Kees Cook
next prev parent reply other threads:[~2020-09-06 20:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-06 14:20 [RFC PATCH 0/9] Fork brute force attack mitigation (fbfam) John Wood
2020-09-06 16:11 ` John Wood
2020-09-06 20:25 ` Kees Cook [this message]
2020-09-07 18:07 ` John Wood
-- strict thread matches above, loose matches on Subject: below --
2020-09-06 12:15 John Wood
2020-09-06 13:52 ` John Wood
2020-09-06 14:11 ` John Wood
2020-09-06 14:11 ` John Wood
2020-09-06 14:12 ` John Wood
2020-09-06 14:13 ` John Wood
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=202009061323.75C4EC509F@keescook \
--to=keescook@chromium.org \
--cc=john.wood@gmx.com \
--cc=kernel-hardening@lists.openwall.com \
/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.