From 82da4ed18f5682c0cc76cd435b6de2459c7b5f83 Mon Sep 17 00:00:00 2001 From: Patrick Schleizer Date: Thu, 28 Jul 2022 09:56:24 -0400 Subject: [PATCH] comments --- .../dracut/modules.d/40cold-boot-attack-defense/wipe-ram.sh | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/usr/lib/dracut/modules.d/40cold-boot-attack-defense/wipe-ram.sh b/usr/lib/dracut/modules.d/40cold-boot-attack-defense/wipe-ram.sh index 3019ab0..1f7566c 100755 --- a/usr/lib/dracut/modules.d/40cold-boot-attack-defense/wipe-ram.sh +++ b/usr/lib/dracut/modules.d/40cold-boot-attack-defense/wipe-ram.sh @@ -59,7 +59,7 @@ ram_wipe() { if [ "$dmsetup_actual_output" = "$dmsetup_expected_output" ]; then echo "INFO: wipe-ram.sh: Success, there are no more mounted encrypted disks, OK." > /dev/kmsg - + ## This should probably be removed in production? sleep 3 else echo "\ @@ -68,7 +68,7 @@ WARNING: wipe-ram.sh:There are still mounted encrypted disks! RAM wipe failed! debugging information: dmsetup_expected_output: '$dmsetup_expected_output' dmsetup_actual_output: '$dmsetup_actual_output'" > /dev/kmsg - + ## How else could the user be informed that something is wrong? sleep 5 fi