On Fri, Mar 31, 2017 at 05:15:29PM +0200, Markus Niebel wrote: > Am Freitag, den 31.03.2017, 16:49 +0200 schrieb Michael Olbrich: > > On Fri, Mar 31, 2017 at 04:30:48PM +0200, Markus Niebel wrote: > > > From: Markus Niebel <[email protected]> > > > > > > regarding to https://www.kernel.org/doc/Documentation/Changes > > > kernel needs openssl to compile since v4.3 > > > > I think the documentation is a bit misleading. Since v4.3 it needs openssl > > development packages _if_ module signing is enabled. Or have you seen > > anything else that needs openssl? > > If not, then this should be an option like KERNEL_LZOP. > > > > log just from our buildserver (linux 4.6): > > HOSTCC scripts/extract-cert > scripts/sign-file.c:25:30: fatal error: openssl/opensslv.h: No such file or > directory > #include <openssl/opensslv.h> > ^ > compilation terminated. > scripts/extract-cert.c:21:25: fatal error: openssl/bio.h: No such file or > directory > #include <openssl/bio.h> > ^ > compilation terminated. > make[2]: *** [scripts/sign-file] Error 1 > > The compilation is triggered by > > hostprogs-$(CONFIG_SYSTEM_TRUSTED_KEYRING) += extract-cert > > So I think this is (potentially) wider use case. I'm not the expert for > this kind of stuff. Can send v2 with same approach as KERNEL_LZOP
This is for module/image signing and for integrity stuff like IMA. I don't think this is always needed. So please provide a v2. mfg, Michael -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ ptxdist mailing list [email protected]
