opened 07:04AM - 17 Apr 25 UTC
I tried to install and run `ram-wipe` lately. The installation was done via self…-built packages from repositories: https://github.com/Kicksecure/ram-wipe (from commit `99cddffc08041eb896cc4295e118a9831bf50d0a`) and https://github.com/Kicksecure/helper-scripts (from commit `7534ee5874277fdebce8d91bebee7e0b02c8acdc`). The installation went without errors. But when rebooting and powering on I did not notice anything apart from:
```bash
[ 350.165760] cold-boot-attack-defense-kexec-prepare[3815]: INFO: wiperamaction: reboot
[ 350.184377] cold-boot-attack-defense-kexec-prepare[3815]: 'disabled' (mokutil_output: 'SecureBoot disabled')
[ OK ] Stopped ram-wipe-kexec-prepare.ser�.|oot Attack Defense Reboot RAM Wipe.
```
The result is different from [what was expected](https://www.kicksecure.com/wiki/Ram-wipe#Sample_Printout).
I did not add any Linux Kernel boot arguments during tests. I did not use Secure Boot or any encrypted partitions during tests. The tests were done on Debian Trixie. The question is, are Secure Boot, encrypted partitions or any Linux Kernel boot arguments required for `ram-wipe` to launch? Because [the installation guide](https://www.kicksecure.com/wiki/Ram-wipe) did not mention anything related directly, but from brief code exploration I know that Secure Boot is being checked and the entire `ram-wipe` relies on Kernel boot args.
I am going to look closer on `ram-wipe` code, as well as check, whether RAM is actually being zeroed, but any help will be appreciated.