From mboxrd@z Thu Jan  1 00:00:00 1970
Reply-To: kernel-hardening@lists.openwall.com
References: <CAGXu5jJXpnaKsG_W_xzwr0SBkKSEtUqEC0LR3-ZByPx9NAj5Lw@mail.gmail.com>
From: Richard Weinberger <richard@nod.at>
Message-ID: <565B822B.8000700@nod.at>
Date: Sun, 29 Nov 2015 23:54:35 +0100
MIME-Version: 1.0
In-Reply-To: <CAGXu5jJXpnaKsG_W_xzwr0SBkKSEtUqEC0LR3-ZByPx9NAj5Lw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: [kernel-hardening] Re: status: GRKERNSEC_BRUTE
To: Kees Cook <keescook@chromium.org>
Cc: "kernel-hardening@lists.openwall.com" <kernel-hardening@lists.openwall.com>
List-ID: <kernel-hardening.lists.openwall.com>

Am 24.11.2015 um 20:19 schrieb Kees Cook:
> Hi,
> 
> While not strictly a _kernel_ self-protection mechanism, it's still
> something that I'd love to see upstream, so I'll ping about its status
> here too. :) Any updates on the brute force detector? (Last week I had
> someone suggest making this a "respawn cgroup" or something, if it's
> not workable as-is.) Anything we can help with?

I can revive my patch and resend. Maybe it helps to collect
new ideas (or NAKs ;)).

Thanks,
//richard