linux-kernel - Re: [PATCH v9] HP BIOSCFG driver

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: <0b92276d-09e5-4308-b4c1-4519ac2ac65d@t-8ch.de>
Date:   Fri, 14 Apr 2023 22:36:02 +0200
From:   Thomas Weißschuh <thomas@...ch.de>
To:     Jorge Lopez <jorgealtxwork@...il.com>
Cc:     hdegoede@...hat.com, platform-driver-x86@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v9] HP BIOSCFG driver - Documentation

On 2023-04-14 15:00:02-0500, Jorge Lopez wrote:
> On Fri, Apr 14, 2023 at 10:27 AM <thomas@...ch.de> wrote:
> > On 2023-04-12 09:48:21-0500, Jorge Lopez wrote:
> > > [..]
> > >
> > > +What:                /sys/class/firmware-attributes/*/authentication/SPM/statusbin
> > > +Date:                March 29
> > > +KernelVersion:       5.18
> > > +Contact:     "Jorge Lopez" <jorge.lopez2@...com>
> > > +Description: 'statusbin' is a read-only file that returns 'status' information
> > > +             in binary format. This file provides a mechanism for components
> > > +             downstream (e.g. Recovery Agent) can read the status and public
> > > +             key modulus.
> >
> > This is still missing docs about how to interpret the contents of the
> > "statusbin" file.
> >
> > "components downstream" -> userspace.
> >
> 
> I will provide the details in Version 10.   Additionally, I am working
> with the architect to understand the need for 'statusbin' in their
> upcoming features.

If the userspace component is not ready maybe this can be delayed for a
future patchset?
The basic features should already be useful with a generic client like
fwupd.
Doing it in steps should be faster both in development and wall time.

> > I think we can start with the code review.
> >
> 
> I will send all files with Version 10.   To aid in the review process,
> I will keep all ..c in separate reviews.  It is less confusing that
> way since there is commonality between them
> 
> > Could you also provide a sample of the attribute files?
> > I'm especially curious about the different instances of the sure-start
> > attributes, including current_value, possible_values and the auditlog
> > properties.
> >
> 
> What type of sample are you looking for.?   I can provide you with a
> tree display of all attributes and some output samples for different
> attribute types.

That sounds great.

> I will include sure-start  attributes, including current_value,
> possible_values and the audit log properties.  Please let me know if
> there is anything else you want to see.

I want to get a feeling for the exposed bios settings and how the
sure-start stuff works.

> > Also is the userspace component for this published somewhere?
> > If so it would be useful to refer to it from the commit message.
> 
> Linux components are under development and not published yet.  The
> only linux component at this time is the driver (hp bioscfg).
> The only published components are under Windows ONLY.

Maybe mention this in the commit message.

Also it would be useful to test the new driver with fwupd which is the
existing userspace user of this ABI.
Just to make sure that nothing is obviously broken there.
(And mention this in the commit message)

Thomas