Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 9 Nov 2020 19:23:48 +0100
From: John Wood <>
To: Randy Dunlap <>, Kees Cook <>,
	Jann Horn <>
Cc: John Wood <>, Jonathan Corbet <>,
	James Morris <>,
	"Serge E. Hallyn" <>,,,,
Subject: Re: [PATCH v2 7/8] Documentation: Add documentation for the Brute LSM

Thanks for the typos corrections. Will be corrected in the next patch

On Sun, Nov 08, 2020 at 08:31:13PM -0800, Randy Dunlap wrote:
> So an app could read crash_period_threshold and just do a new fork every
> threshold + 1 time units, right? and not be caught?

Yes, you are right. But we must set a crash_period_threshold that does not
make an attack feasible. For example, with the default value of 30000 ms,
an attacker can break the app only once every 30 seconds. So, to guess
canaries or break ASLR, the attack needs a big amount of time. But it is

So, I think that to avoid this scenario we can add a maximum number of
faults per fork hierarchy. Then, the mitigation will be triggered if the
application crash period falls under the period threshold or if the number
of faults exceed the maximum commented.

This way, if an attack is of long duration, it will also be detected and

What do you think?

> thanks for the documentation.
> --
> ~Randy

John Wood

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.