[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <555C3BFF.4030304@suse.cz>
Date: Wed, 20 May 2015 15:47:11 +0800
From: Michal Marek <mmarek@...e.cz>
To: David Howells <dhowells@...hat.com>, Theodore Ts'o <tytso@....edu>
CC: Andy Lutomirski <luto@...capital.net>,
Andy Lutomirski <luto@...nel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
David Woodhouse <dwmw2@...radead.org>,
Abelardo Ricart III <aricart@...nix.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Sedat Dilek <sedat.dilek@...il.com>, keyrings@...ux-nfs.org,
Rusty Russell <rusty@...tcorp.com.au>,
LSM List <linux-security-module@...r.kernel.org>,
Borislav Petkov <bp@...en8.de>, Jiri Kosina <jkosina@...e.cz>
Subject: Re: Should we automatically generate a module signing key at all?
Dne 20.5.2015 v 00:23 David Howells napsal(a):
> For my own purposes when running kernels on my test machines, I build kernels
> with all the necessary drivers built in and boot them directly out of the
> build tree by PXE. Then I copy any modules I'm testing by scp and use them.
> I don't generally use signed modules anymore because the modules aren't signed
> during the build phase but rather during the module installation phase (which
> isn't of any use to me).
If you really wanted, you could do
make INSTALL_MOD_PATH=$pwd/tmp modules_install
and then scp the (signed) module tree in ./tmp.
Michal
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists