All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petko Manolov <petkan@mip-labs.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: dhowells@redhat.com, rusty@rustcorp.com.au, mmarek@suse.cz,
	mjg59@srcf.ucam.org, keyrings@linux-nfs.org,
	dmitry.kasatkin@gmail.com, mcgrof@suse.com,
	linux-kernel@vger.kernel.org, seth.forshee@canonical.com,
	linux-security-module@vger.kernel.org
Subject: Re: [PATCH 10/8] modsign: Allow password to be specified for signing key
Date: Tue, 19 May 2015 19:34:27 +0300	[thread overview]
Message-ID: <20150519163427.GA7718@localhost> (raw)
In-Reply-To: <1432052112.3277.66.camel@infradead.org>

On 15-05-19 17:15:12, David Woodhouse wrote:
> On Tue, 2015-05-19 at 18:50 +0300, Petko Manolov wrote:
> > On 15-05-19 15:45:58, David Woodhouse wrote:
> > > We don't want this in the Kconfig since it might then get exposed in
> > > /proc/config.gz. So make it a parameter to Kbuild instead. This also
> > > means we don't have to jump through hoops to strip quotes from it, as
> > > we would if it was a config option.
> > 
> > If it were on a network-less, secure sign/build server i'd say it is OK.  
> > 
> > However, exposing your private key's password in an environment variable on a 
> > regular Linux box is a bit fishy.
> 
> I don't quite understand the objection.
> 
> If you want the modules to be signed with an external key of your
> choice, then for the duration of the 'make modules_sign' run (or 'make
> modules_install if CONFIG_MODULE_SIG_ALL=y) surely the password has to
> be available *somehow*? 
> 
> You are, of course, free to sign the modules by invoking sign-file
> directly. In which case you *still* need to provide it with the password
> for the key somehow, if there is one.
> 
> Mimi quite rightly pointed out that my original mechanism for this, a
> CONFIG_MODULE_SIG_KEY_PASSWORD option, was inadvertently exposing it
> more than was necessary.
> 
> As it is now, you *only* need it in the environment for the duration of
> the operations that actually *use* it.

As with everything there is bad and good side to your proposal.

bad:
  - password in environment variable _could_ be very dangerous;
  - someone is bound to misuse this feature sooner or later;

good:
  - the actual risk is mitigated as the key is very short-lived;
  - the feature is going to be used by a small number of people;
  - does not break automated builds, maybe;
  - there is an alternative for those who want more secure approach;

> Do you have a better suggestion?

*better* is a matter of prospective.  Security and convenience are at the wrong 
side of the spectrum relative to each other. :)

Don't get me wrong, your patch is perhaps the lesser evil.  I just wanted to 
bring up my concerns.


cheers,
Petko

  reply	other threads:[~2015-05-19 16:35 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-15 12:35 [PATCH 0/8] MODSIGN: Use PKCS#7 for module signatures [ver #4] David Howells
2015-05-15 12:35 ` [PATCH 1/8] X.509: Extract both parts of the AuthorityKeyIdentifier " David Howells
2015-05-15 12:35 ` [PATCH 2/8] X.509: Support X.509 lookup by Issuer+Serial form " David Howells
2015-05-15 12:35 ` [PATCH 3/8] PKCS#7: Allow detached data to be supplied for signature checking purposes " David Howells
2015-05-15 12:35 ` [PATCH 4/8] MODSIGN: Provide a utility to append a PKCS#7 signature to a module " David Howells
2015-05-20  0:50   ` Andy Lutomirski
2015-05-20 13:14     ` David Howells
2015-05-20 16:00       ` Andy Lutomirski
2015-05-15 12:36 ` [PATCH 5/8] MODSIGN: Use PKCS#7 messages as module signatures " David Howells
2015-05-15 12:36 ` [PATCH 6/8] sign-file: Add option to only create signature file " David Howells
2015-05-15 19:07   ` sign-file and detached PKCS#7 firmware signatures David Howells
2015-05-18 23:13     ` Luis R. Rodriguez
2015-05-19  9:25       ` David Howells
2015-05-19 16:19         ` Luis R. Rodriguez
2015-05-19 16:48           ` David Howells
2015-05-19 18:21             ` Luis R. Rodriguez
2015-05-19 18:35             ` Luis R. Rodriguez
2015-05-19 18:47               ` David Howells
2015-05-19 20:12                 ` Luis R. Rodriguez
2015-05-19 20:29                   ` David Howells
2015-05-15 12:36 ` [PATCH 7/8] system_keyring.c doesn't need to #include module-internal.h [ver #4] David Howells
2015-05-15 12:36 ` [PATCH 8/8] MODSIGN: Extract the blob PKCS#7 signature verifier from module signing " David Howells
2015-05-15 13:46 ` [PATCH 0/8] MODSIGN: Use PKCS#7 for module signatures " David Woodhouse
2015-05-15 16:52 ` [PATCH 1/4] modsign: Abort modules_install when signing fails David Woodhouse
2015-05-19  1:29   ` Mimi Zohar
2015-05-19  6:40     ` Woodhouse, David
2015-05-19 11:45       ` Mimi Zohar
2015-05-19 12:57         ` Woodhouse, David
2015-05-19 13:54           ` Mimi Zohar
2015-05-15 16:53 ` [PATCH 2/4] modsign: Allow external signing key to be specified David Woodhouse
2015-05-15 16:53 ` [PATCH 3/4] modsign: Allow password to be specified for signing key David Woodhouse
2015-05-19  1:37   ` Mimi Zohar
2015-05-15 16:54 ` [PATCH 4/4] modsign: Allow signing key to be PKCS#11 David Woodhouse
2015-05-18 12:43   ` David Howells
2015-05-15 22:51 ` [PATCH 0/8] MODSIGN: Use PKCS#7 for module signatures [ver #4] Rusty Russell
2015-05-19 14:45 ` [PATCH 9/8] modsign: Abort modules_install when signing fails David Woodhouse
2015-05-19 14:45 ` [PATCH 10/8] modsign: Allow password to be specified for signing key David Woodhouse
2015-05-19 15:36   ` David Howells
2015-05-19 15:50   ` Petko Manolov
2015-05-19 16:15     ` David Woodhouse
2015-05-19 16:34       ` Petko Manolov [this message]
2015-05-19 18:39   ` Mimi Zohar
2015-05-19 18:48     ` David Howells
2015-05-19 19:14       ` Mimi Zohar
2015-05-19 20:04         ` David Woodhouse
2015-05-19 14:46 ` [PATCH 11/8] modsign: Allow signing key to be PKCS#11 David Woodhouse
2015-05-19 14:46 ` [PATCH 12/8] modsign: Allow external signing key to be specified David Woodhouse
2015-05-19 14:47 ` [PATCH 13/8] modsign: Extract signing cert from CONFIG_MODULE_SIG_KEY if needed David Woodhouse
2015-05-20  0:36 ` [PATCH 0/8] MODSIGN: Use PKCS#7 for module signatures [ver #4] Andy Lutomirski
2015-05-20 13:36   ` David Howells
2015-05-20 15:56     ` Andy Lutomirski
2015-05-20 16:21       ` Petko Manolov
2015-05-20 16:41         ` Andy Lutomirski
2015-05-20 16:55           ` Petko Manolov
2015-05-21 21:38         ` Luis R. Rodriguez
2015-05-21 21:44           ` Andy Lutomirski
2015-05-21 21:59             ` Luis R. Rodriguez
2015-05-21 22:06               ` Andy Lutomirski
2015-05-21 22:16                 ` Luis R. Rodriguez
2015-05-21 22:24                   ` Andy Lutomirski
2015-05-21 22:31                     ` Luis R. Rodriguez
2015-05-21 22:47                       ` Andy Lutomirski
2015-05-21 23:01                         ` Luis R. Rodriguez
2015-05-21 23:09                           ` Andy Lutomirski
2015-05-22  7:56                             ` David Howells
2015-05-22 12:42                               ` Mimi Zohar
2015-05-22  7:49             ` David Howells
2015-05-22  7:48           ` David Howells
2015-05-22 12:28             ` Mimi Zohar
2015-05-24 10:52               ` Petko Manolov
2015-05-21 13:59       ` David Howells

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=20150519163427.GA7718@localhost \
    --to=petkan@mip-labs.com \
    --cc=dhowells@redhat.com \
    --cc=dmitry.kasatkin@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=keyrings@linux-nfs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=mcgrof@suse.com \
    --cc=mjg59@srcf.ucam.org \
    --cc=mmarek@suse.cz \
    --cc=rusty@rustcorp.com.au \
    --cc=seth.forshee@canonical.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.