From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752522Ab3LLXuq (ORCPT ); Thu, 12 Dec 2013 18:50:46 -0500 Received: from mail-pd0-f176.google.com ([209.85.192.176]:42319 "EHLO mail-pd0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751979Ab3LLXum (ORCPT ); Thu, 12 Dec 2013 18:50:42 -0500 Message-ID: <52AA4BC8.1080207@gmail.com> Date: Fri, 13 Dec 2013 10:50:32 +1100 From: Ryan Mallon User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: Kees Cook , "Theodore Ts'o" , vegard.nossum@oracle.com, LKML , Tommi Rantala , Ingo Molnar , "Eric W. Biederman" , Andy Lutomirski , Daniel Vetter , Alan Cox , Greg Kroah-Hartman , Jason Wang , "David S. Miller" , Dan Carpenter , James Morris Subject: Re: [PATCH 1/9] Known exploit detection References: <1386867152-24072-1-git-send-email-vegard.nossum@oracle.com> <20131212190659.GG13547@thunk.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 13/12/13 08:13, Kees Cook wrote: > On Thu, Dec 12, 2013 at 11:06 AM, Theodore Ts'o wrote: >> On Thu, Dec 12, 2013 at 05:52:24PM +0100, vegard.nossum@oracle.com wrote: >>> From: Vegard Nossum >>> >>> The idea is simple -- since different kernel versions are vulnerable to >>> different root exploits, hackers most likely try multiple exploits before >>> they actually succeed. > > I like this idea. It serves a few purposes, not the least of which is > very clearly marking in code where we've had problems, regardless of > the fact that it reports badness to the system owner. And I think > getting any additional notifications about bad behavior is a nice idea > too. Though, if an attacker is running through a series of exploits, and one eventually succeeds then the first thing to do would be to clean traces of the _exploit() notifications from the syslog. Since running through a series of exploits is pretty quick, this can probably all be done before the sysadmin ever notices. The _exploit() notifications could also be used to spam the syslogs. Although they are individually ratelimited, if there are enough _exploit() markers in the kernel then an annoying person can cycle through them all to generate large amounts of useless syslog. ~Ryan