linux-kernel - Re: [PATCH v6 01/11] kconfig: Add PicoSAT interface

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] [day] [month] [year] [list]

Message-ID: <CA+i-1C0HUE2+TmMMthRv1MCSQg4SX-+oZao9-4M3rKg71oA-5A@mail.gmail.com>
Date: Mon, 13 Jan 2025 17:29:39 +0100
From: Brendan Jackman <jackmanb@...gle.com>
To: Luis Chamberlain <mcgrof@...nel.org>
Cc: ole0811sch@...il.com, deltaone@...ian.org, jan.sollmann@....de, 
	jude.gyimah@....de, linux-kbuild@...r.kernel.org, 
	linux-kernel@...r.kernel.org, masahiroy@...nel.org, nathan@...nel.org, 
	nicolas@...sle.eu, thorsten.berger@....de
Subject: Re: [PATCH v6 01/11] kconfig: Add PicoSAT interface

On Fri, 10 Jan 2025 at 20:15, Luis Chamberlain <mcgrof@...nel.org> wrote:
>
> On Thu, Jan 09, 2025 at 01:28:17PM +0000, Brendan Jackman wrote:
> > Would it be easy enough to provide this support as a standalone binary that can
> > be called from scripts/config too?
>
> I suspect this begs more the question of how could this be useful
> outside of xconfig.

I was thinking of something like like this:

$ scripts/sat_config --interactive --enable KVM_AMD

This would then prompt the user with a range of solutions for getting
KVM_AMD enabled.

Then there might be an "I'm feeling lucky" variant like:

$ scripts/sat_config --first-solution --enable KVM_AMD

Where instead of prompting the user it just picks some arbitrary or
"minimal" set of changes that leads to KVM_AMD being enabled.

> But one step at a time, this can be done *after*
> this initial patch set gets merged,

Totally, please consider this a "yes, and" not a "but".