public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Stuge <peter@stuge.se>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] patch linux-mod.eclass to add support for module signing
Date: Wed, 6 Mar 2013 23:14:10 +0100	[thread overview]
Message-ID: <20130306221410.7910.qmail@stuge.se> (raw)
In-Reply-To: <CA+ZvHYE0TPv5rt5tfb_6YJe=aNnkMr5onFQVvfCL04Tx7t=fbg@mail.gmail.com>

Carlos Silva wrote:
> > > If one wants to create a key himself, it's also possible to use this
> > > key, he just has to name it signing_key.priv and siging_key.x509 and
> > > put it under /usr/src/linux.
> >
> > Do you know if this is a sane default?
> >
> > Where do most users of signed modules store keys so far?
> 
> It's where the kernel build system picks them.

Are you sure? I find that hard to believe? Even if I tell an external
module to build against a source tree in ~/linux/ the Makefiles will
go to look for the keys in /usr/src/linux/ ?


> They only have to be there to build the kernel, nothing else.

I'm not talking about end users, by users I mean those who use the
key files to build kernels and modules.


//Peter


  reply	other threads:[~2013-03-06 22:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-06 19:25 [gentoo-dev] [RFC] patch linux-mod.eclass to add support for module signing Carlos Silva
2013-03-06 19:32 ` Steev Klimaszewski
2013-03-06 19:54   ` Carlos Silva
2013-03-06 21:39 ` Peter Stuge
2013-03-06 22:07   ` Carlos Silva
2013-03-06 22:14     ` Peter Stuge [this message]
2013-03-06 22:19       ` Carlos Silva
2013-03-08 17:44 ` [gentoo-dev] " Steven J. Long

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130306221410.7910.qmail@stuge.se \
    --to=peter@stuge.se \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox