| lists.openwall.net | 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 linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Tue, 30 Jun 2009 23:43:53 -0700 From: Jeremy Maitin-Shepard <jeremy@...emyms.com> To: Nigel Cunningham <ncunningham@...a.org.au> Cc: tuxonice-devel@...ts.tuxonice.net, linux-kernel@...r.kernel.org Subject: Re: [TuxOnIce-devel] RFC: Suspend-to-ram cold boot protection by encrypting page cache Nigel Cunningham <ncunningham@...a.org.au> writes: > Hi Jeremy. > I'd suggest emailing the Linux-PM list rather than tuxonice-devel. > TuxOnIce devel focuses on the out-of-vanilla suspend to disk > enhancements rather than on suspend to ram. The Linux-PM list is a good suggestion, but I specifically included tuxonice because of the note at the bottom --- namely that I believe that tuxonice in particular already includes support for much of what is needed to implement the idea. Specifically, suppose right at the stage in tuxonice hibernation when the kernel as about to write the page cache pages to disk, it instead just encrypts in place those pages, clears the encryption key, then waits for the userspace helper to pass it back the key again to use to decrypt the pages. In fact it would seems that actually entering S3 is mostly irrelevant in terms of the implementation. Tuoxnice already has code to deal with interfacing with a userspace helper that is kept unfrozen (and its pages handled specially) while everything else is frozen and the page cache is overwritten, which is precisely what is needed for this idea. In particular, it seems that an implementation of the idea I proposed would look a lot like tuxonice with a powerdown mode of entering S3, just that instead of writing the page cache to disk, it is encrypted in place. I suppose it could well be that all of the facilities used by tuxonice to do this are actually already in the kernel, in which case it is indeed not relevant to tuxonice, but it is not clear that the uswsusp infrastructure has everything that is needed. -- Jeremy Maitin-Shepard -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists