lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Tue, 26 Mar 2019 11:06:13 +0100
From:   Boris Petkov <>
To:     "Lendacky, Thomas" <>,
        "Singh, Brijesh" <>
CC:     lijiang <>,
        "" <>,
        "" <>,
        "" <>,
        "" <>,
        "" <>, "" <>,
        "" <>,
        "" <>,
        "" <>
Subject: Re: [PATCH 1/3] kexec: Do not map the kexec area as decrypted when SEV is active

On March 25, 2019 8:59:28 PM GMT+01:00, "Lendacky, Thomas" <> wrote:
>Maybe what would help is to describe why there is a difference between
>and SEV in regards to kexec. During a traditional boot under SME, SME
>encrypt the kernel, so the SME kexec kernel also needs to be
>in order to replicate a normal SME boot. During a traditional boot
>SEV, the kernel has already been loaded encrypted, so the SEV kexec
>needs to be encrypted in order to replicate a normal SEV boot.

Yah, that should be in a comment above that function.


Sent from a small device: formatting sux and brevity is inevitable. 

Powered by blists - more mailing lists