linux-kernel - CONFIG_* used by user-space to figure out whether a feature is on/off

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 15 Jul 2013 11:40:50 -0400
From:	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: CONFIG_* used by user-space to figure out whether a feature is on/off

Hey Linus,

I am hoping you can help me draw an understanding and a line in sand whether:
 a) Tools should not depend on /proc/config.gz to figure out whether
    a kernel has some CONFIG_X=y feature.

 b) If they are OK to do so, what do we do when certain CONFIG_X options
    get reworked/removed. Would they be considered regressions? Aka
    is this similar to 'you shall not break user-space'?


Irrespective of that, do you have any ideas of how a user-space program (say GRUB)
can figure out whether the configuration stanze it generates is supported by
the kernel. If you don't want to answer this question - since this might
open a can of worms you prefer not to deal with - that is absolutly OK.

Folks have been tossing ideas such as:
 - Let the user deal with it and if it does not boot - oh well.
 - readelf or objdump.
 - use /boot/config-<kernel>-<version> as most (all?) distros stick that in
   there.

Thanks!
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/