linux-kernel - Re: [PATCH v4 02/12] kconfig: Add picosat.c (1/3)

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: <ZsPBfBQXNZmbNfpE@bombadil.infradead.org>
Date: Mon, 19 Aug 2024 15:04:44 -0700
From: Luis Chamberlain <mcgrof@...nel.org>
To: Ole Schuerks <ole0811sch@...il.com>
Cc: masahiroy@...nel.org, deltaone@...ian.org, jan.sollmann@....de,
	jude.gyimah@....de, linux-kbuild@...r.kernel.org,
	linux-kernel@...r.kernel.org, thorsten.berger@....de
Subject: Re: [PATCH v4 02/12] kconfig: Add picosat.c (1/3)

On Fri, Aug 16, 2024 at 12:20:01PM +0200, Ole Schuerks wrote:
> What's the best way of letting the user know that they need to 
> install PicoSAT if they want to use the conflict resolver?
> My idea would 
> be to notify the user via the GUI when they try to use the interface of 
> the conflict resolver without having PicoSAT installed. Do you see any 
> issues with that/do you prefer some alternative approach?

Conflicts don't happen often and we already have a printf which happens when
one does, my recommendation would be that we simply opt-in for the
resolver if the user has the requirements installed. Otherwise we only
inform the user to install it if a conflict comes up. Documentation can
also be enhanced to describe this functionality / support.

  Luis