Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934814Ab2KBSbC (ORCPT ); Fri, 2 Nov 2012 14:31:02 -0400 Received: from mx1.redhat.com ([209.132.183.28]:43097 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933068Ab2KBSa7 (ORCPT ); Fri, 2 Nov 2012 14:30:59 -0400 Date: Fri, 2 Nov 2012 14:30:51 -0400 From: Vivek Goyal To: Jiri Kosina Cc: Matthew Garrett , linux-kernel@vger.kernel.org, linux-security-module@vger.kernel.org, linux-efi@vger.kernel.org Subject: Re: [RFC] Second attempt at kernel secure boot support Message-ID: <20121102183051.GO3300@redhat.com> References: <1348152065-31353-1-git-send-email-mjg@redhat.com> <20121029174131.GC7580@srcf.ucam.org> <20121031150201.GA12394@srcf.ucam.org> <20121102153047.GF3300@redhat.com> <20121102154248.GA7681@srcf.ucam.org> <20121102155247.GH3300@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 860 Lines: 28 On Fri, Nov 02, 2012 at 05:22:41PM +0100, Jiri Kosina wrote: > On Fri, 2 Nov 2012, Vivek Goyal wrote: > > > > > "crash" utility has module which allows reading kernel memory. So leaking > > > > this private key will be easier then you are thinking it to be. > > > > > > That's not upstream, right? > > > > Yes, checked with Dave, it is not upstream. Well, still it is a concern > > for distro kernel. > > Well, that's about /dev/crash, right? Yes, I was talking about /dev/crash. > > How about /proc/kcore? Yes, we will have to lock down /proc/kcore too if we go the private key solution way. Thanks Vivek -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/