linux-kernel - Re: [SPECIFICATION RFC] The firmware and bootloader log specification

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: <20201207215032.GN32272@bill-the-cat>
Date:   Mon, 7 Dec 2020 16:50:32 -0500
From:   Tom Rini <trini@...sulko.com>
To:     Paul Menzel <pmenzel@...gen.mpg.de>
Cc:     Wim Vervoorn <wvervoorn@...an.com>,
        The development of GNU GRUB <grub-devel@....org>,
        Daniel Kiper <daniel.kiper@...cle.com>, coreboot@...eboot.org,
        LKML <linux-kernel@...r.kernel.org>,
        systemd-devel@...ts.freedesktop.org,
        trenchboot-devel@...glegroups.com,
        U-Boot Mailing List <u-boot@...ts.denx.de>, x86@...nel.org,
        xen-devel@...ts.xenproject.org, alecb@...ss.edu,
        alexander.burmashev@...cle.com, allen.cryptic@...il.com,
        andrew.cooper3@...rix.com, ard.biesheuvel@...aro.org,
        "btrotter@...il.com" <btrotter@...il.com>,
        dpsmith@...rtussolutions.com, eric.devolder@...cle.com,
        eric.snowberg@...cle.com, hpa@...or.com, hun@...imensional.de,
        javierm@...hat.com, joao.m.martins@...cle.com,
        kanth.ghatraju@...cle.com, konrad.wilk@...cle.com,
        krystian.hebel@...eb.com, leif@...iainc.com,
        lukasz.hawrylko@...el.com, luto@...capital.net,
        michal.zygowski@...eb.com, Matthew Garrett <mjg59@...gle.com>,
        mtottenh@...mai.com,
        Vladimir 'phcoder' Serbinenko <phcoder@...il.com>,
        piotr.krol@...eb.com, pjones@...hat.com, roger.pau@...rix.com,
        ross.philipson@...cle.com, tyhicks@...ux.microsoft.com,
        Heinrich Schuchardt <xypron.glpk@....de>
Subject: Re: [SPECIFICATION RFC] The firmware and bootloader log specification

On Fri, Dec 04, 2020 at 02:23:23PM +0100, Paul Menzel wrote:
> Dear Wim, dear Daniel,
> 
> 
> First, thank you for including all parties in the discussion.
> Am 04.12.20 um 13:52 schrieb Wim Vervoorn:
> 
> > I agree with you. Using an existing standard is better than inventing
> > a new one in this case. I think using the coreboot logging is a good
> > idea as there is indeed a lot of support already available and it is
> > lightweight and simple.
> In my opinion coreboot’s format is lacking, that it does not record the
> timestamp, and the log level is not stored as metadata, but (in coreboot)
> only used to decide if to print the message or not.
> 
> I agree with you, that an existing standard should be used, and in my
> opinion it’s Linux message format. That is most widely supported, and
> existing tools could then also work with pre-Linux messages.
> 
> Sean Hudson from Mentor Graphics presented that idea at Embedded Linux
> Conference Europe 2016 [1]. No idea, if anything came out of that effort.
> (Unfortunately, I couldn’t find an email. Does somebody have contacts at
> Mentor to find out, how to reach him?)

I believe the main thing that came out of this was the reminder that
there was an even older attempt by U-Boot to have such a mechanism, and
that at the time getting the work accepted in Linux faced some hurdles
or another.

That said, I too agree with taking what's already a de facto standard,
the coreboot logging, and expand on it as needed.

-- 
Tom

Download attachment "signature.asc" of type "application/pgp-signature" (660 bytes)