[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150102225420.GC29018@amd>
Date: Fri, 2 Jan 2015 23:54:20 +0100
From: Pavel Machek <pavel@....cz>
To: Jiri Kosina <jkosina@...e.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 2015-01-02 23:49:52, Jiri Kosina wrote:
> On Fri, 2 Jan 2015, Pavel Machek wrote:
>
> > > You also want to protect against binaries that are evil on purpose,
> > > right?
> >
> > Umm. No. Not by default. We don't want to break crashme or trinity by
> > default.
>
> I thought trinity is issuing syscalls directly (would make more sense than
> going through glibc, wouldn't it?) ... haven't checked the source though.
Patch in this thread wanted to insert delays into kernel on SIGSEGV
processing. That's bad idea by default.
But changing glibc to do sleep(30); abort(); instead of abort(); to
slow down bruteforcing of canaries makes some kind of sense... and
should be ok by default.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
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