linux-kernel - Re: tip: bzip2/lzma now in tip:x86/setup-lzma

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:	Mon, 05 Jan 2009 14:11:27 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Alain Knaff <alain@...ff.lu>
CC:	the arch/x86 maintainers <x86@...nel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: tip: bzip2/lzma now in tip:x86/setup-lzma

Alain Knaff wrote:
> H. Peter Anvin wrote:
>> Well, I think the right thing to do at this stage is to simply compress
>> the initramfs with the preferred compression method (and if no
>> compression method is provided, with none.)  This can be relatively
>> simply done with a script, I think.
> 
> Well, the problem is there is really no "preferred" method for the
> ramdisk or initramfs. And picking the one from the kernel might not
> work, because the user might have chosen to compress the kernel via
> bzip2, but only allowed lzma and gzip for the ramdisk.
> 

I'm thinking that with "preferred" we might just use the first one in 
the priority list "lzma, bzip2, gzip, uncompressed" depending on what is 
installed in the kernel.

Using the kernel method may definitely not work, especially on 
architectures which don't do this style of kernel compression.

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