public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Abelardo Ricart III <aricart@memnix.com>
To: David Howells <dhowells@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Michal Marek <mmarek@suse.cz>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	LSM List <linux-security-module@vger.kernel.org>,
	Rusty Russell <rusty@rustcorp.com.au>,
	keyrings@linux-nfs.org, James Morris <james.l.morris@oracle.com>,
	Sedat Dilek <sedat.dilek@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] MODSIGN: Change default key details [ver #2]
Date: Tue, 05 May 2015 18:44:28 -0400	[thread overview]
Message-ID: <1430865868.5842.8.camel@memnix.com> (raw)
In-Reply-To: <16633.1430836479@warthog.procyon.org.uk>

On Tue, 2015-05-05 at 15:34 +0100, David Howells wrote:
> Abelardo Ricart III <aricart@memnix.com> wrote:
> 
> > Here's a (barely tested) patch to show what I mean with the config option. 
> > The
> > default case is to always generate a new key at build 
> > (MODULE_SIG_BUILDGEN=y)
> > and fallback on generating keys during build only if one doesn't exist
> > (MODULE_SIG_BUILDGEN=n). 
> 
> Does it cope with randconfig?
> 
> David

Well it would only depend on MODULE_SIG, and switching it on and off again
would do exactly what it says it's going to do: either regenerate the signing
keys every time, or don't if they already exist.

I would have to actually change the logic slightly so it works strictly as
intended though. So no, this isn't merge-able at all.

I was more wondering if implementing something to this effect would be okay, so
we can strictly define the behavior at build time (no surprises).

  reply	other threads:[~2015-05-05 22:44 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-30 13:58 [PATCH] MODSIGN: Change default key details [ver #2] David Howells
2015-04-30 14:39 ` Sedat Dilek
2015-04-30 14:50   ` David Howells
2015-04-30 17:49     ` Sedat Dilek
2015-04-30 18:00       ` Linus Torvalds
2015-05-01 21:41         ` Abelardo Ricart III
2015-05-02  4:12           ` Linus Torvalds
2015-05-02  6:57             ` Sedat Dilek
2015-05-02  9:46             ` Abelardo Ricart III
2015-05-04  1:45               ` Linus Torvalds
2015-05-04  4:42                 ` Abelardo Ricart III
     [not found]                   ` <CA+55aFzYUsXHC=_RiQFBhMmDxrFT4bqNP5F0LGWUu7Hc9sXBFQ@mail.gmail.com>
2015-05-04  7:18                     ` Abelardo Ricart III
2015-05-04 21:40                     ` Abelardo Ricart III
2015-05-05 14:34                       ` David Howells
2015-05-05 22:44                         ` Abelardo Ricart III [this message]
2015-05-04 18:45                 ` Linus Torvalds
2015-05-05 14:33                   ` David Howells
2015-05-05 14:37                     ` David Howells
2015-05-05 14:43                     ` Linus Torvalds
2015-05-05 15:30                       ` David Howells
2015-05-05 15:22                   ` Michal Marek
2015-05-05 15:41                     ` Linus Torvalds
2015-05-06 12:20                       ` Michal Marek
2015-05-07 11:00                         ` David Howells
2015-05-07 12:15                           ` Michal Marek
2015-05-07 12:24                             ` Michal Marek
2015-05-08 13:05                               ` David Howells
2015-05-12  8:51                                 ` Michal Marek
2015-05-15 15:21                                   ` David Howells
2015-05-19 14:14                                   ` David Howells
2015-05-19 15:19                                     ` David Woodhouse
2015-05-18 16:07                             ` David Woodhouse
2015-05-16 15:39                   ` David Woodhouse
2015-05-18 10:47                     ` David Howells
2015-05-18 10:56                       ` David Howells
2015-05-18 11:13                       ` David Woodhouse
2015-05-19  2:14                         ` Mimi Zohar
2015-05-20 10:17           ` David Woodhouse
2015-05-20 10:51             ` David Howells
2015-05-20 11:08               ` David Woodhouse
2015-05-20 11:26             ` [PATCH] modsign: Use single PEM file for autogenerated key David Woodhouse
2015-05-20 14:56               ` David Howells
2015-05-20 15:18                 ` David Woodhouse
2015-05-21 11:31                 ` David Woodhouse

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=1430865868.5842.8.camel@memnix.com \
    --to=aricart@memnix.com \
    --cc=dhowells@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=james.l.morris@oracle.com \
    --cc=keyrings@linux-nfs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=mmarek@suse.cz \
    --cc=rusty@rustcorp.com.au \
    --cc=sedat.dilek@gmail.com \
    --cc=torvalds@linux-foundation.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