From mboxrd@z Thu Jan 1 00:00:00 1970 From: Richard Weinberger Subject: Re: [PATCH] [RFC] Deter exploit bruteforcing Date: Sat, 03 Jan 2015 00:00:22 +0100 Message-ID: <54A72306.2050908@nod.at> References: <1419457167-15042-1-git-send-email-richard@nod.at> <20150102051142.GF4873@amd> <54A67A38.3000207@nod.at> <20150102194616.GA27538@amd> <54A7103E.6020500@nod.at> <20150102222936.GA29018@amd> <20150102224646.GB29018@amd> <20150102225420.GC29018@amd> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: Kees Cook , LKML , "linux-fsdevel@vger.kernel.org" , David Rientjes , Aaron Tomlin , DaeSeok Youn , Thomas Gleixner , vdavydov@parallels.com, Rik van Riel , Oleg Nesterov , Andrew Morton , Peter Zijlstra , Ingo Molnar , Al Viro , Andy Lutomirski , Brad Spengler To: Pavel Machek , Jiri Kosina Return-path: In-Reply-To: <20150102225420.GC29018@amd> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Am 02.01.2015 um 23:54 schrieb Pavel Machek: > 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. No. This is not what this patch does. > 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. As I saidn only focusing one the specific stack canary case is not enough. Thanks, //richard