linux-kernel - Re: [PATCH -tip] x86: headers - fix export private data to userspace

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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 13 Jan 2009 21:50:13 +0300
From:	Cyrill Gorcunov <gorcunov@...il.com>
To:	Harvey Harrison <harvey.harrison@...il.com>
Cc:	Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Sam Ravnborg <sam@...nborg.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Jaswinder Singh Rajput <jaswinderlinux@...il.com>
Subject: Re: [PATCH -tip] x86: headers - fix export private data to
	userspace

[Harvey Harrison - Tue, Jan 13, 2009 at 10:37:12AM -0800]
| On Tue, 2009-01-13 at 21:34 +0300, Cyrill Gorcunov wrote:
| > Impact: cleanup
| 
| > 4) setup.h - COMMAND_LINE_SIZE saved for userspace, bootloaders
| >    could use it.
| 
| Doesn't this need to be (at least) _COMMAND_LINE_SIZE to avoid
| polluting the namespace, not sure it can be changed though as the
| horse is already out of the barn.
| 
| Harvey
| 

I was concerning more about lilo side, is it use this param.
So here is a link

	http://lists.linuxcoding.com/kernel/2006-q3/msg18665.html

is seems LILO has it's own definition for COMMAND_LINE_SIZE.
On the other hand it touches boot protocol. Peter should know
if it safe to hide/change COMMAND_LINE_SIZE. Peter?

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