linux-kernel - Re: [PATCH] [REPOST] x86_64, i386: Add command line length to boot protocol

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: <45F9D974.1050309@zytor.com>
Date:	Thu, 15 Mar 2007 16:40:36 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Alon Bar-Lev <alon.barlev@...il.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] [REPOST] x86_64, i386: Add command line length to boot
 protocol

Alon Bar-Lev wrote:
> Hello,
> 
> I really don' t understand why you insist that the boot protocol
>> =2.02 had 255 limit!
> Please remove this from the description.
> You want to add size, that's OK, but please don't mess with previous
> definitions.
> Boot protocol 2.02 introduced the null terminated string truncated by
> kernel, which can be at any size.
> 

Well, except for a very brief window, the limit *was* 255.  If the boot 
loader wants to verify nontruncation, this is a valid concern.

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