Received: by 2002:a25:c205:0:0:0:0:0 with SMTP id s5csp217029ybf; Thu, 27 Feb 2020 19:37:38 -0800 (PST) X-Google-Smtp-Source: APXvYqzyt6QdVNmvCziCIFDt5XJqwrkPp+1McY84iP2fyoo89MXwU95AoDBauwVTeVA4a0m8AejY X-Received: by 2002:aca:75d2:: with SMTP id q201mr1127172oic.81.1582861058285; Thu, 27 Feb 2020 19:37:38 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1582861058; cv=none; d=google.com; s=arc-20160816; b=yC+5Me6ir+3FfLhGcG1NxnUHMBhGkr+22r+BN6ecnwO69r9GZ0h0FFAufFhK2XZdHR xDFnscA69QaXqL6RYaONHaMkg/qEe5bd/C9nrtMmGrrC+7NBEmO6zs7iXT8N6hh42MHy B9/42+2A4+65A2yABmu+4Vl0JdU6XggxezfEcsgx9NXs2w4RaKlWigxh0fOdC7P0yuvw xtU93oyQE8c9UWyNNm52BRMHEJN+ihtVitMtN4j/u0QXqS/lOyEF0f+NzkFvwVrpKQEG H8WCAAUPXeWaTLQPWelj5lxVkOJK0fp7Gc75fm7QB5mzFdraLyiEOMSyxWIbGfrVMg51 l73w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=aDJjztBIb3g7WuQ8tm9j5jVgnbmxznk84OuAMLjRbBQ=; b=HGLgP4rzwyY0EZmNmgq2qyUhVq+R24DeQyCPXWp5T3xAMEIVR3aiSSEvM6hgKU0e5C 0msB/G2wHVxZoukRTxsKTBbWv0vhVgseSLBUrvYURnufp8LQSsk/OXB3wY0xc7WxIIla QHX+PJzQ9eH21R3S0GdcGFTaXPuHRWrrFW+ZG35sC8hS+zatl9ozW/zNsip6MFpR/8X+ RGqtWaYkr1F4rYivurLhW8FpKzGM5rzuwcE2CH6VdAejwDraRjZl0W1XTZ6nZOaGAlDY TuBaqrZzxE4IwF5eKk+iuceG7H/Rv8oeW3YGWqQQkI0zDxfRJX1+K7+n68JMluENUx+L Zb8A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=OJ7Z5xT8; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id l4si1107452oib.170.2020.02.27.19.37.26; Thu, 27 Feb 2020 19:37:38 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=OJ7Z5xT8; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730779AbgB1DhC (ORCPT + 99 others); Thu, 27 Feb 2020 22:37:02 -0500 Received: from us-smtp-delivery-1.mimecast.com ([207.211.31.120]:57023 "EHLO us-smtp-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1730630AbgB1DhC (ORCPT ); Thu, 27 Feb 2020 22:37:02 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1582861021; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=aDJjztBIb3g7WuQ8tm9j5jVgnbmxznk84OuAMLjRbBQ=; b=OJ7Z5xT8kgtMXRIZOYfxNCfKkLv5Sbffh+O4OLYmv7legVzzY5N4ziVV5LnbWBvrolKVyy iQN5whzpD2El2X9cbczqtxB8HH5QQaqFJW7XMYvPvf5Jxjr3sGJ9UVJiSNBy7bTniKEQPj gYQDXTqPmwi9dAwJg32mcbyYjD5dIjU= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-1-RILYYk35OgShqd8ub0Y2sA-1; Thu, 27 Feb 2020 22:36:57 -0500 X-MC-Unique: RILYYk35OgShqd8ub0Y2sA-1 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 0C33B10509B8; Fri, 28 Feb 2020 03:36:55 +0000 (UTC) Received: from localhost (ovpn-12-49.pek2.redhat.com [10.72.12.49]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 36AE45D9CD; Fri, 28 Feb 2020 03:36:50 +0000 (UTC) Date: Fri, 28 Feb 2020 11:36:48 +0800 From: Baoquan He To: Kees Cook Cc: Kristen Carlson Accardi , dyoung@redhat.com, tglx@linutronix.de, mingo@redhat.com, bp@alien8.de, hpa@zytor.com, arjan@linux.intel.com, rick.p.edgecombe@intel.com, x86@kernel.org, linux-kernel@vger.kernel.org, kernel-hardening@lists.openwall.com, kexec@lists.infradead.org Subject: Re: [RFC PATCH 09/11] kallsyms: hide layout and expose seed Message-ID: <20200228033648.GJ24216@MiWiFi-R3L-srv> References: <20200205223950.1212394-1-kristen@linux.intel.com> <20200205223950.1212394-10-kristen@linux.intel.com> <202002060428.08B14F1@keescook> <20200227024253.GA5707@MiWiFi-R3L-srv> <202002270802.1CA8B32AC@keescook> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <202002270802.1CA8B32AC@keescook> User-Agent: Mutt/1.10.1 (2018-07-13) X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 02/27/20 at 08:02am, Kees Cook wrote: > On Thu, Feb 27, 2020 at 10:42:53AM +0800, Baoquan He wrote: > > On 02/06/20 at 09:51am, Kristen Carlson Accardi wrote: > > > On Thu, 2020-02-06 at 04:32 -0800, Kees Cook wrote: > > > > > > In the past, making kallsyms entirely unreadable seemed to break > > > > weird > > > > stuff in userspace. How about having an alternative view that just > > > > contains a alphanumeric sort of the symbol names (and they will > > > > continue > > > > to have zeroed addresses for unprivileged users)? > > > > > > > > Or perhaps we wait to hear about this causing a problem, and deal > > > > with > > > > it then? :) > > > > > > > > > > Yeah - I don't know what people want here. Clearly, we can't leave > > > kallsyms the way it is. Removing it entirely is a pretty fast way to > > > figure out how people use it though :). > > > > Kexec-tools and makedumpfile are the users of /proc/kallsyms currently. > > We use kallsyms to get page_offset_base and _stext. > > AIUI, those run as root so they'd be able to consume the uncensored > output. Yes, they have to be run under root.