From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264122AbTDWQdz (ORCPT ); Wed, 23 Apr 2003 12:33:55 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264123AbTDWQdy (ORCPT ); Wed, 23 Apr 2003 12:33:54 -0400 Received: from almesberger.net ([63.105.73.239]:6661 "EHLO host.almesberger.net") by vger.kernel.org with ESMTP id S264122AbTDWQdf (ORCPT ); Wed, 23 Apr 2003 12:33:35 -0400 Date: Wed, 23 Apr 2003 13:45:30 -0300 From: Werner Almesberger To: Julien Oster Cc: Robert Love , Julien Oster , linux-kernel@vger.kernel.org Subject: Re: kernel ring buffer accessible by users Message-ID: <20030423134530.C3557@almesberger.net> References: <1051031876.707.804.camel@localhost> <20030423125602.B1425@almesberger.net> <20030423160556.GA30306@frodo.midearth.frodoid.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030423160556.GA30306@frodo.midearth.frodoid.org>; from frodoid@frodoid.org on Wed, Apr 23, 2003 at 06:05:56PM +0200 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Julien Oster wrote: > Of course one could say "then let's just stop writing out anything in > the kernel buffer that COULD be sensitive", but I think this would > actually castrate the meaning of such a buffer. It's also bad security design to try to plug hundreds of potential leaks, instead of the one common channel they share. > And there's stillt he possibility to tweak the permissions for > dmesg so that only a certain group (staff, operator, adm...) can execute > it, but then setuid root. Yes, but you'll get quite a few objections to adding yet another suid root program :-) - Werner -- _________________________________________________________________________ / Werner Almesberger, Buenos Aires, Argentina wa@almesberger.net / /_http://www.almesberger.net/____________________________________________/