All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mimi Zohar <zohar@linux.ibm.com>
To: linux-kselftest@vger.kernel.org, Shuah Khan <shuah@kernel.org>
Cc: linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
	Mimi Zohar <zohar@linux.ibm.com>
Subject: [PATCH v2 0/5] selftests/ima: add kexec and kernel module tests
Date: Tue, 26 Feb 2019 18:26:55 -0500	[thread overview]
Message-ID: <1551223620-11586-1-git-send-email-zohar@linux.ibm.com> (raw)

The kernel can be configured to require kexec kernel images and kernel
modules are signed.  An IMA policy can be specified on the boot command
line or a custom IMA policy loaded requiring the kexec kernel image and
kernel modules be signed.  In addition, systems booted in secure boot
mode with the IMA architecture specific policy enabled, require validly
signed kexec kernel images and kernel modules.

There are two methods of signing kernel images and two methods of
signing kernel modules.  In addition, there are two syscalls for each.

kernel image:  PE signature, IMA signature
kexec syscalls: kexec_load, kexec_file_load

Both the PE and IMA kernel image signature can only be verified when
loaded via the kexec_file_load syscall.

kernel moodule: appended signature, IMA signature
kernel module syscalls: init_module, finit_module

The appended kernel module signature can be verified when the kernel
module is loaded via either syscall.  The IMA kernel module signature
can only be verified when the kernel module is loaded via the
finit_module syscall.

The selftests in this patch set verify that only signed kernel images
and kernel modules are loaded as required, based on the kernel config,
the secure boot mode, and the IMA runtime policy.

Loading a kernel image or kernel module requires root privileges.  To
run just the IMA selftests: sudo make TARGETS=ima kselftest

Mimi Zohar (5):
  selftests/ima: cleanup the kexec selftest
  selftests/ima: define a set of common functions
  selftests/ima: define common logging functions
  selftests/ima: kexec_file_load syscall test
  selftests/ima: loading kernel modules

 tools/testing/selftests/ima/Makefile               |   3 +-
 tools/testing/selftests/ima/common_lib.sh          | 154 ++++++++++++++++
 tools/testing/selftests/ima/test_kernel_module.sh  |  96 ++++++++++
 .../testing/selftests/ima/test_kexec_file_load.sh  | 195 +++++++++++++++++++++
 tools/testing/selftests/ima/test_kexec_load.sh     |  53 ++----
 5 files changed, 463 insertions(+), 38 deletions(-)
 create mode 100755 tools/testing/selftests/ima/common_lib.sh
 create mode 100755 tools/testing/selftests/ima/test_kernel_module.sh
 create mode 100755 tools/testing/selftests/ima/test_kexec_file_load.sh

-- 
2.7.5


WARNING: multiple messages have this Message-ID (diff)
From: zohar at linux.ibm.com (Mimi Zohar)
Subject: [PATCH v2 0/5] selftests/ima: add kexec and kernel module tests
Date: Tue, 26 Feb 2019 18:26:55 -0500	[thread overview]
Message-ID: <1551223620-11586-1-git-send-email-zohar@linux.ibm.com> (raw)

The kernel can be configured to require kexec kernel images and kernel
modules are signed.  An IMA policy can be specified on the boot command
line or a custom IMA policy loaded requiring the kexec kernel image and
kernel modules be signed.  In addition, systems booted in secure boot
mode with the IMA architecture specific policy enabled, require validly
signed kexec kernel images and kernel modules.

There are two methods of signing kernel images and two methods of
signing kernel modules.  In addition, there are two syscalls for each.

kernel image:  PE signature, IMA signature
kexec syscalls: kexec_load, kexec_file_load

Both the PE and IMA kernel image signature can only be verified when
loaded via the kexec_file_load syscall.

kernel moodule: appended signature, IMA signature
kernel module syscalls: init_module, finit_module

The appended kernel module signature can be verified when the kernel
module is loaded via either syscall.  The IMA kernel module signature
can only be verified when the kernel module is loaded via the
finit_module syscall.

The selftests in this patch set verify that only signed kernel images
and kernel modules are loaded as required, based on the kernel config,
the secure boot mode, and the IMA runtime policy.

Loading a kernel image or kernel module requires root privileges.  To
run just the IMA selftests: sudo make TARGETS=ima kselftest

Mimi Zohar (5):
  selftests/ima: cleanup the kexec selftest
  selftests/ima: define a set of common functions
  selftests/ima: define common logging functions
  selftests/ima: kexec_file_load syscall test
  selftests/ima: loading kernel modules

 tools/testing/selftests/ima/Makefile               |   3 +-
 tools/testing/selftests/ima/common_lib.sh          | 154 ++++++++++++++++
 tools/testing/selftests/ima/test_kernel_module.sh  |  96 ++++++++++
 .../testing/selftests/ima/test_kexec_file_load.sh  | 195 +++++++++++++++++++++
 tools/testing/selftests/ima/test_kexec_load.sh     |  53 ++----
 5 files changed, 463 insertions(+), 38 deletions(-)
 create mode 100755 tools/testing/selftests/ima/common_lib.sh
 create mode 100755 tools/testing/selftests/ima/test_kernel_module.sh
 create mode 100755 tools/testing/selftests/ima/test_kexec_file_load.sh

-- 
2.7.5

WARNING: multiple messages have this Message-ID (diff)
From: zohar@linux.ibm.com (Mimi Zohar)
Subject: [PATCH v2 0/5] selftests/ima: add kexec and kernel module tests
Date: Tue, 26 Feb 2019 18:26:55 -0500	[thread overview]
Message-ID: <1551223620-11586-1-git-send-email-zohar@linux.ibm.com> (raw)
Message-ID: <20190226232655.Cpc-zSBzd-Pr-IcXDGvG7vZOmd44tvAuMZ2dIAMFpyA@z> (raw)

The kernel can be configured to require kexec kernel images and kernel
modules are signed.  An IMA policy can be specified on the boot command
line or a custom IMA policy loaded requiring the kexec kernel image and
kernel modules be signed.  In addition, systems booted in secure boot
mode with the IMA architecture specific policy enabled, require validly
signed kexec kernel images and kernel modules.

There are two methods of signing kernel images and two methods of
signing kernel modules.  In addition, there are two syscalls for each.

kernel image:  PE signature, IMA signature
kexec syscalls: kexec_load, kexec_file_load

Both the PE and IMA kernel image signature can only be verified when
loaded via the kexec_file_load syscall.

kernel moodule: appended signature, IMA signature
kernel module syscalls: init_module, finit_module

The appended kernel module signature can be verified when the kernel
module is loaded via either syscall.  The IMA kernel module signature
can only be verified when the kernel module is loaded via the
finit_module syscall.

The selftests in this patch set verify that only signed kernel images
and kernel modules are loaded as required, based on the kernel config,
the secure boot mode, and the IMA runtime policy.

Loading a kernel image or kernel module requires root privileges.  To
run just the IMA selftests: sudo make TARGETS=ima kselftest

Mimi Zohar (5):
  selftests/ima: cleanup the kexec selftest
  selftests/ima: define a set of common functions
  selftests/ima: define common logging functions
  selftests/ima: kexec_file_load syscall test
  selftests/ima: loading kernel modules

 tools/testing/selftests/ima/Makefile               |   3 +-
 tools/testing/selftests/ima/common_lib.sh          | 154 ++++++++++++++++
 tools/testing/selftests/ima/test_kernel_module.sh  |  96 ++++++++++
 .../testing/selftests/ima/test_kexec_file_load.sh  | 195 +++++++++++++++++++++
 tools/testing/selftests/ima/test_kexec_load.sh     |  53 ++----
 5 files changed, 463 insertions(+), 38 deletions(-)
 create mode 100755 tools/testing/selftests/ima/common_lib.sh
 create mode 100755 tools/testing/selftests/ima/test_kernel_module.sh
 create mode 100755 tools/testing/selftests/ima/test_kexec_file_load.sh

-- 
2.7.5

             reply	other threads:[~2019-02-26 23:27 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-26 23:26 Mimi Zohar [this message]
2019-02-26 23:26 ` [PATCH v2 0/5] selftests/ima: add kexec and kernel module tests Mimi Zohar
2019-02-26 23:26 ` zohar
2019-02-26 23:26 ` [PATCH v2 1/5] selftests/ima: cleanup the kexec selftest Mimi Zohar
2019-02-26 23:26   ` Mimi Zohar
2019-02-26 23:26   ` zohar
2019-02-27  0:57   ` shuah
2019-02-27  0:57     ` shuah
2019-02-27  0:57     ` shuah
2019-02-26 23:26 ` [PATCH v2 2/5] selftests/ima: define a set of common functions Mimi Zohar
2019-02-26 23:26   ` Mimi Zohar
2019-02-26 23:26   ` zohar
2019-02-27  1:01   ` shuah
2019-02-27  1:01     ` shuah
2019-02-27  1:01     ` shuah
2019-02-28 19:54   ` Petr Vorel
2019-02-28 19:54     ` Petr Vorel
2019-02-28 19:54     ` pvorel
2019-02-26 23:26 ` [PATCH v2 3/5] selftests/ima: define common logging functions Mimi Zohar
2019-02-26 23:26   ` Mimi Zohar
2019-02-26 23:26   ` zohar
2019-02-27  1:39   ` shuah
2019-02-27  1:39     ` shuah
2019-02-27  1:39     ` shuah
2019-02-28 20:18   ` Petr Vorel
2019-02-28 20:18     ` Petr Vorel
2019-02-28 20:18     ` pvorel
2019-02-28 21:01   ` Petr Vorel
2019-02-28 21:01     ` Petr Vorel
2019-02-28 21:01     ` pvorel
2019-02-26 23:26 ` [PATCH v2 4/5] selftests/ima: kexec_file_load syscall test Mimi Zohar
2019-02-26 23:26   ` Mimi Zohar
2019-02-26 23:26   ` zohar
2019-02-27  1:54   ` shuah
2019-02-27  1:54     ` shuah
2019-02-27  1:54     ` shuah
2019-02-28 22:00   ` Petr Vorel
2019-02-28 22:00     ` Petr Vorel
2019-02-28 22:00     ` pvorel
2019-03-10 17:48     ` Mimi Zohar
2019-03-10 17:48       ` Mimi Zohar
2019-03-10 17:48       ` zohar
2019-03-11  8:34       ` Petr Vorel
2019-03-11  8:34         ` Petr Vorel
2019-03-11  8:34         ` pvorel
2019-03-11 11:49         ` Mimi Zohar
2019-03-11 11:49           ` Mimi Zohar
2019-03-11 11:49           ` zohar
2019-02-28 22:20   ` Petr Vorel
2019-02-28 22:20     ` Petr Vorel
2019-02-28 22:20     ` pvorel
2019-02-26 23:27 ` [PATCH v2 5/5] selftests/ima: loading kernel modules Mimi Zohar
2019-02-26 23:27   ` Mimi Zohar
2019-02-26 23:27   ` zohar
2019-02-27  1:59   ` shuah
2019-02-27  1:59     ` shuah
2019-02-27  1:59     ` shuah
2019-02-27 14:14     ` Mimi Zohar
2019-02-27 14:14       ` Mimi Zohar
2019-02-27 14:14       ` zohar
2019-02-27 15:33       ` shuah
2019-02-27 15:33         ` shuah
2019-02-27 15:33         ` shuah
2019-02-27 18:37         ` Mimi Zohar
2019-02-27 18:37           ` Mimi Zohar
2019-02-27 18:37           ` zohar
2019-02-28 23:14         ` Petr Vorel
2019-02-28 23:14           ` Petr Vorel
2019-02-28 23:14           ` pvorel
2019-02-28 22:32   ` Petr Vorel
2019-02-28 22:32     ` Petr Vorel
2019-02-28 22:32     ` pvorel
2019-03-10 17:48     ` Mimi Zohar
2019-03-10 17:48       ` Mimi Zohar
2019-03-10 17:48       ` zohar

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=1551223620-11586-1-git-send-email-zohar@linux.ibm.com \
    --to=zohar@linux.ibm.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=shuah@kernel.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 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.