linux-kernel - Re: [BOOTLOADER SPECIFICATION RFC] The bootloader log format for TrenchBoot and others

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: <7FE0DF48-C221-460E-99D5-00E42128283C@amacapital.net>
Date:   Fri, 29 May 2020 10:11:40 -0700
From:   Andy Lutomirski <luto@...capital.net>
To:     Daniel Kiper <daniel.kiper@...cle.com>
Cc:     grub-devel@....org, linux-kernel@...r.kernel.org,
        trenchboot-devel@...glegroups.com, x86@...nel.org,
        xen-devel@...ts.xenproject.org, alec.brown@...cle.com,
        alexander.burmashev@...cle.com, andrew.cooper3@...rix.com,
        ard.biesheuvel@...aro.org, dpsmith@...rtussolutions.com,
        eric.snowberg@...cle.com, hpa@...or.com, javierm@...hat.com,
        kanth.ghatraju@...cle.com, konrad.wilk@...cle.com,
        krystian.hebel@...eb.com, leif@...iainc.com,
        lukasz.hawrylko@...ux.intel.com, michal.zygowski@...eb.com,
        mjg59@...gle.com, mtottenh@...mai.com, phcoder@...il.com,
        piotr.krol@...eb.com, pjones@...hat.com, ross.philipson@...cle.com
Subject: Re: [BOOTLOADER SPECIFICATION RFC] The bootloader log format for TrenchBoot and others



> On May 29, 2020, at 4:30 AM, Daniel Kiper <daniel.kiper@...cle.com> wrote:
> 
> Hey,
> 
> Below you can find my rough idea of the bootloader log format which is
> generic thing but initially will be used for TrenchBoot work. I discussed
> this proposal with Ross and Daniel S. So, the idea went through initial
> sanitization. Now I would like to take feedback from other folks too.
> So, please take a look and complain...

> In general we want to pass the messages produced by the bootloader to the OS
> kernel and finally to the userspace for further processing and analysis. Below
> is the description of the structures which will be used for this thing.

Is the intent for a human to read these, or to get them into the system log file, or are they intended to actually change the behavior of the system?

IOW, what is this for?