From 72f4b38de5dd9af18d89f899e832c8dbd54f6cd9 Mon Sep 17 00:00:00 2001 From: Chris Murphy Date: May 28 2020 18:39:06 +0000 Subject: formatting 3 --- diff --git a/hibernationstatus.md b/hibernationstatus.md index f192921..b082535 100644 --- a/hibernationstatus.md +++ b/hibernationstatus.md @@ -40,6 +40,8 @@ We would like to see an install time means of enabling hibernation retained via - signed and encrypted hibernation image [4]; +*Note:* This is the most central nugget needed for limited hibernation support. + **Nice to have enhancements to hibernation:** - dynamic swapfiles created and enabled prior to hibernation entry [5]; @@ -66,7 +68,6 @@ https://lwn.net/Articles/820870/ [4] It's not enough to encrypt swap because encryption alone provides no integrity. Even though there is an authentication component to the encryption, the image can't be said to be authentic -- as-in trustworthy. To provide the required trust and confidentiality, the hibernation image needs to be signed and encrypted. Joey Lee @ SUSE recently confirmed this is the latest status of that work: https://lkml.org/lkml/2019/7/10/601 -This is the most central nugget that's needed to get to limited hibernation support. [5] Developing this means hibernation could be enabled post-install, and more easily serve competing use cases. Use cases that don't need hibernation avoid the space wasted for a dedicated and unused swap partition. Use cases that need hibernation can be supported without a swap partition being created at install time.