ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] [TECH TOPIC] live kernel patching
Date: Tue, 6 May 2014 09:16:48 -0400	[thread overview]
Message-ID: <20140506131648.GA16222@redhat.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1405060901460.3969@pobox.suse.cz>

On Tue, May 06, 2014 at 09:05:53AM +0200, Jiri Kosina wrote:
 > On Mon, 5 May 2014, Kees Cook wrote:
 > 
 > > I'm very interested in this, especially as it may relate to security 
 > > exploit mitigation work, both in the sense of being able to arbitrarily 
 > > patch the kernel against flaws, and to defend against attackers being 
 > > able to ... er ... arbitrarily patch the kernel... :)
 > 
 > :) Well, for performing the patching, the attacker would either have to be 
 > able to modprobe module (kpatch, kgraft, ksplice) or kexec to a new kernel 
 > (criu-based solution). In either case, the system would be owned anyway 
 > already, independently on any live patching mechanism.

being root doesn't mean "can patch the kernel" if in secure boot mode.
(Or at least is going to need special considerations regarding signing).

	Dave

  reply	other threads:[~2014-05-06 13:16 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-02 19:42 Jiri Kosina
2014-05-02 21:17 ` James Bottomley
2014-05-04  8:34 ` Li Zefan
2014-05-05 14:00 ` Chris Mason
2014-05-05 21:58   ` Andy Lutomirski
2014-05-05 22:08     ` Jiri Kosina
2014-05-06 13:17       ` James Bottomley
2014-05-06 13:23       ` Pavel Emelyanov
2014-05-06 14:07     ` Chris Mason
2014-05-06 15:44       ` Pavel Emelyanov
2014-05-06 17:02         ` Chris Mason
2014-05-06  1:33 ` Kees Cook
2014-05-06  7:05   ` Jiri Kosina
2014-05-06 13:16     ` Dave Jones [this message]
2014-05-06 13:23       ` Jiri Kosina
2014-05-06 13:18     ` Kees Cook
2014-05-06 13:28       ` James Bottomley
2014-05-06 13:41         ` Kees Cook
2014-05-06 17:11           ` Mimi Zohar
2014-05-06 18:34           ` James Bottomley
2014-05-06 12:30 ` Masami Hiramatsu

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=20140506131648.GA16222@redhat.com \
    --to=davej@redhat.com \
    --cc=jkosina@suse.cz \
    --cc=ksummit-discuss@lists.linuxfoundation.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