DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:
	mime-version:content-type:content-transfer-encoding:
	content-disposition:references;
	b=PJ988aMxCvdKbpcb/DbktXWhO+qK0VvSqp38LcxipftRqiKyMyAWLF0WBdR99cj0G
	gsDDj6wSlgM5r2FdrFzgQ==
Message-ID: <d43160c70609161748n2af1c88cx33344e7da3e2b302@mail.google.com>
Date: Sat, 16 Sep 2006 20:48:26 -0400
From: rossb <rossb@google.com>
To: "Arjan van de Ven" <arjan@infradead.org>
Subject: Re: + allow-proc-configgz-to-be-built-as-a-module.patch added to -mm tree
Cc: "Randy.Dunlap" <rdunlap@xenotime.net>, linux-kernel@vger.kernel.org,
       akpm@osdl.org, mm-commits@vger.kernel.org, akpm@google.com,
       sam@ravnborg.org
In-Reply-To: <1158407250.5152.60.camel@laptopd505.fenrus.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <200609152158.k8FLw7ud018089@shell0.pdx.osdl.net>
	 <20060915154752.d7bdb8a0.rdunlap@xenotime.net>
	 <1158407250.5152.60.camel@laptopd505.fenrus.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1444
Lines: 32

On 9/16/06, Arjan van de Ven <arjan@infradead.org> wrote:
> > > In some ways this is a bit risky, because the .config which is used for
> > > compiling kernel/configs.c isn't necessarily the same as the .config which was
> > > used to build vmlinux.
> >
> > and that's why a module wasn't allowed.
> > It's not worth the risk IMO.

The problem is, the patch is basically s/bool/tristate/ so you can't
really count on /proc/config.gz anyway.  It's a lot like security
through obscurity.

> One hack we could do is make an md5sum or similar of the config and
> stick that somewhere which is built in and always available (proc or
> sysfs or something like that); that can be used to validate any config
> basically to be "correct matching". In fact we could even make it
> (optionally) part of the VERMAGIC to avoid any kind of mismatch at all.

Not a bad idea, but I think you want to be able to edit your config
before compiling modules.  In particular, you might want to turn
something from off to module.

How about we embed the md5sum of the config in the kernel, make it
available via /proc or /sysfs and then have /proc/config.gz return an
error in the event the md5sum doesn't match?

    Ross
-
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/