[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKTCnzkkxTDO_CST79YHuKQF_xOFAA4LCZjsRSO1bcM7B3qgBw@mail.gmail.com>
Date: Wed, 17 Dec 2014 09:12:09 +0530
From: Balbir Singh <bsingharora@...il.com>
To: Seth Jennings <sjenning@...hat.com>
Cc: Josh Poimboeuf <jpoimboe@...hat.com>,
Jiri Kosina <jkosina@...e.cz>,
Vojtech Pavlik <vojtech@...e.cz>,
Steven Rostedt <rostedt@...dmis.org>,
Petr Mladek <pmladek@...e.cz>, Miroslav Benes <mbenes@...e.cz>,
Christoph Hellwig <hch@...radead.org>,
Greg KH <gregkh@...uxfoundation.org>,
Andy Lutomirski <luto@...capital.net>,
Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
live-patching@...r.kernel.org, x86@...nel.org, kpatch@...hat.com,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCHv7 0/3] Kernel Live Patching
On Wed, Dec 17, 2014 at 12:35 AM, Seth Jennings <sjenning@...hat.com> wrote:
> On Tue, Dec 16, 2014 at 11:45:12PM +0530, Balbir Singh wrote:
>> On Tue, Dec 16, 2014 at 11:28 PM, Seth Jennings <sjenning@...hat.com> wrote:
>> >
>> > Changelog:
>> >
>> > Thanks for all the feedback!
>> >
>>
>> Could you describe what this does to signing? I presume the patched
>> module should cause a taint on module signing?
>
> The patch module can be signed to avoid the taint of being unsigned,
> assuming you have the signing key for the kernel you are running.
> However we do taint with a new taint flag (see 1/3) to indicate
> that the kernel has been patched.
>
I see, so the assumption is that the module and patch would be signed
with the same key?
Thanks,
Balbir Singh.
--
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