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: <479FA428.3040806@zytor.com>
Date:	Tue, 29 Jan 2008 14:09:44 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Ian Campbell <ijc@...lion.org.uk>
CC:	Jeremy Fitzhardinge <jeremy@...p.org>,
	linux-kernel@...r.kernel.org,
	"Eric W. Biederman" <ebiederm@...ssion.com>
Subject: Re: PATCH/RFC: bzImage payload as compressed ELF file.

Ian Campbell wrote:
> On Tue, 2008-01-29 at 13:50 -0800, H. Peter Anvin wrote:
>> Ian Campbell wrote:
>>> I finessed the length issue slightly since it happens that the word
>>> before the payload is the payload's length. I'm mulling a variety of
>>> options:
>>>       * declare it compression scheme dependant. At least for gzip
>> it
>>>         knows when it has reached the end.
>>>       * codify the length followed by data thing we happen to have
>> now
>>>       * add a length field to the header, using another 4 bytes (is
>>>         there any pressure on the size of the header?).
>>>
>>> I'd probably go with the later unless we are pressed for space in
>> the
>>> header.
>> I would agree with that.  In fact, while we're adding fields to the 
>> header, I would like to add a field that would be the CRC32 (or other 
>> simple integrity check) over the whole image.
> 
> As in over the whole compressed payload part? I'll add that while I'm
> there.
> 

I was actually thinking about the whole bzImage.

Obviously, it can't cover itself (unless it's something like a plain 
checksum) so presumably it would compute it with its own field set to zero.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ