[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1432135104.3277.142.camel@infradead.org>
Date: Wed, 20 May 2015 16:18:24 +0100
From: David Woodhouse <dwmw2@...radead.org>
To: David Howells <dhowells@...hat.com>
Cc: Abelardo Ricart III <aricart@...nix.com>,
Michal Marek <mmarek@...e.cz>, torvalds@...ux-foundation.org,
linux-kernel@...r.kernel.org, sedat.dilek@...il.com,
keyrings@...ux-nfs.org, rusty@...tcorp.com.au,
linux-security-module@...r.kernel.org, james.l.morris@...cle.com,
gregkh@...uxfoundation.org
Subject: Re: [PATCH] modsign: Use single PEM file for autogenerated key
On Wed, 2015-05-20 at 15:56 +0100, David Howells wrote:
> David Woodhouse <dwmw2@...radead.org> wrote:
>
> > I am disinclined to put in place any kind of backward-compatibility to
> > find and use the old filenames. And I don't much care about changing the
> > build system 'interface' for the user. I'm *very* keen to break that
> > $(wildcard *.x509) crap anyway, so we might as well do this at the same
> > time.
>
> Should some sort of warning then be emitted if $(wildcard *.x509) *does* turn
> up anything? Just so that people don't get unexpectedly surprised when their
> auxiliary keys are suddenly ignored.
Would people even notice such a warning?
People who are using long-term keys and inserting them into the kernel
build probably ought to be paying attention and know what they're doing.
There are relatively few of them, and I think that as long as the change
is clearly documented, we should probably be fine.
Besides, *anyone* relying on that horrid wildcard crap should have
*expected* it to go away because it was an abomination :)
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@...el.com Intel Corporation
--
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