linux-kernel - Re: [PATCH 0/3] bootconfig: Add value override operator

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: <20200715164504.3400efc5@oasis.local.home>
Date:   Wed, 15 Jul 2020 16:45:04 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Masami Hiramatsu <mhiramat@...nel.org>
Cc:     Alistair Delva <adelva@...gle.com>, linux-doc@...r.kernel.org,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/3] bootconfig: Add value override operator

On Thu, 16 Jul 2020 01:00:21 +0900
Masami Hiramatsu <mhiramat@...nel.org> wrote:

> With this change, if the bootloader wants to change some value
> in the default bootconfig, it doesn't need to parse the existing
> bootconfig, but it can just append the new configs at the tail
> of the bootconfig and update the footer (size, checksum and magic
> word).

I wonder if we should support multiple bootconfigs instead of updating
the size/checksum/magic?

So the end of the initrd would have:

 [data][size/checksum/magic][more-data][size/checksum/magic]


And the kernel could do the following:

 1. read the end of the initrd for bootconfig
 2. If found parse the bootconfig data.
 3. look at the content before the bootconfig
 4. if another bootconfig exists, goto 2.

-- Steve