Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
From:   prakhar srivastava <prsriva02@gmail.com>
Date:   Fri, 10 May 2019 17:16:16 -0700
Message-ID: <CAEFn8q+rT2_0TFb0fKA6ixOvC3H5R5KpR0zFiTOXa_4U-9HeUw@mail.gmail.com>
Subject: Carrying over the ima log during kexec_file_load
To:     linux-kernel@vger.kernel.org, linux-integrity@vger.kernel.org,
        linux-security-module@vger.kernel.org, kexec@lists.infradead.org
Cc:     jmorris@namei.org, Mimi Zohar <zohar@linux.ibm.com>,
        dyoung@redhat.com, bhe@redhat.com, vgoyal@redhat.com
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

Hi,

I am currently looking at carrying over the ima log from the current
kernel to the next kernel during soft reboot(kexec_file_load) for arm64
and x86_64.
During soft reboot(kexec_file_load) TPM boot PCR=E2=80=99s(PCRs 0 through 7=
)
are not reset or extended and thus the boot aggregate does not change,
leaving the new kernel with a sense of secure boot.
During kexec_file_load the kernel file signature is validated through PE
file signature validation.
The boot cmdline args will also be measured with
=E2=80=9Ckexec cmdline buffer measure=E2=80=9D change which is in progress.
https://lkml.org/lkml/2019/5/10/728

Looking at the powerpc implementation of kexec_file_load,  making
change to the kimage_arch as below seems most reasonable.

Struct kimage_arch {
                =E2=80=A6
                ima_log_buffer
                ima_log_buffer_size
};

Add respective entries in dtb/fdt and read the same in the next kernel.
No changes to the purgatory should be needed since no kernel segments
are changed.

Is anyone already looking at this?
If not, I want to understand what=E2=80=99s the best approach for this is?

Thanks,
Prakhar Srivastava