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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <bd4d6c71-c7b7-4986-a215-fcffa1534953@rub.de>
Date: Fri, 7 Feb 2025 16:43:15 +0100
From: Thorsten Berger <thorsten.berger@....de>
To: Brendan Jackman <jackmanb@...gle.com>,
 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
Subject: Re: [PATCH v6 01/11] kconfig: Add PicoSAT interface

Hi Brendan,

Yes, that's a great idea. It reminds me about the eCos configurator 
configtool developed by the Cygnus Solutions developers, which had such 
a capability. One could manually create a partial specification and ask 
it to complete the configuration. We should be able to create such a 
support soon.

We've just created the final set of patches, with the requested changes 
(also some small naming change in the fix generation to avoid 
confusion). Ole is sending them in.

Best, Thorsten



On 13/01/2025 17:29, Brendan Jackman wrote:
> 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".