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>] [day] [month] [year] [list]
Date:	Thu, 22 Jul 2010 19:56:27 +0200
From:	Christoph Anton Mitterer <calestyo@...entia.net>
To:	linux-kernel@...r.kernel.org
Subject: determine the required firmwares for static drivers from .config
 file

Hi.

Just wondered whether it's possible, or someone has already written a
tool, that allows to determine the required firmware (pathnames) for all
statically compiled drivers from a kernel configuration.

Would be interesting to have this in order to automatically add them to
e.g. initramfs images.

Of course it's pretty easy to do this when one has modules (at least for
those using MODULE_FIRMWARE) ;)


Thanks,
Chris.

Download attachment "smime.p7s" of type "application/x-pkcs7-signature" (5672 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ