[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LRH.2.00.1501022331060.30884@twin.jikos.cz>
Date: Fri, 2 Jan 2015 23:32:35 +0100 (CET)
From: Jiri Kosina <jkosina@...e.cz>
To: Pavel Machek <pavel@....cz>
cc: Richard Weinberger <richard@....at>,
Kees Cook <keescook@...omium.org>,
LKML <linux-kernel@...r.kernel.org>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
David Rientjes <rientjes@...gle.com>,
Aaron Tomlin <atomlin@...hat.com>,
DaeSeok Youn <daeseok.youn@...il.com>,
Thomas Gleixner <tglx@...utronix.de>, vdavydov@...allels.com,
Rik van Riel <riel@...hat.com>,
Oleg Nesterov <oleg@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>,
Al Viro <viro@...iv.linux.org.uk>,
Andy Lutomirski <luto@...capital.net>,
Brad Spengler <spender@...ecurity.net>
Subject: Re: [PATCH] [RFC] Deter exploit bruteforcing
On Fri, 2 Jan 2015, Pavel Machek wrote:
> > > Can the slowdown be impelmented in glibc, then?
> >
> > glibc has a lot of asserts where it can detect stack smashing and kills the
> > current process using abort(). Here it could of course also call
> > sleep().
>
> Please do it in glibc, then.
You also want to protect against binaries that are evil on purpose, right?
There is no guarantee that those will calling the kernel through glibc at
all.
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists