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]

Message-ID: <20090113185608.GD14470@localhost>
Date:	Tue, 13 Jan 2009 21:56:08 +0300
From:	Cyrill Gorcunov <gorcunov@...il.com>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Harvey Harrison <harvey.harrison@...il.com>,
	Ingo Molnar <mingo@...e.hu>,
	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

[H. Peter Anvin - Tue, Jan 13, 2009 at 10:54:35AM -0800]
| Cyrill Gorcunov wrote:
| > 
| > 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?
| > 
| 
| Current x86 kernels export the command line size through the bzImage
| header, and as such COMMAND_LINE_SIZE should not be used by userspace.
| 
| I can't speak for other architectures.
| 
| 	-hpa
| 
| -- 
| H. Peter Anvin, Intel Open Source Technology Center
| I work for Intel.  I don't speak on their behalf.
| 

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