Hi, I'm confused about why an encrypted livecd would be an interesting feature. Indeed if encryption is about protection, then I just see 2 ways the livecd cd user can be attacked. - while using the OS (real time personal information handling, like login to gmail.com) - after using the OS (like leaving some kind of history somewhere)
if you consider this, what is the benefit of having the OS encrypted in memory? What kind of attack can be stopped by having encryption rather than a clean OS?
From the network point of view, nothing changes, I do not see any advantages
nor differences.
From the system point of view, as a livecd needs no HD, where would a clear
OS leave some trails or history? Can we reverse magnetic fields of RAM devices? I'm really interested in such topic, please could you explain some scenarios of use/setup in which an encrypted livecd would have advantages over a regular clear livecd? Thanks in advance erick On 6/28/07, Nelson Batalha <[EMAIL PROTECTED]> wrote:
Hi, I think I just finished including encryption in Catalyst (for livecd's). However this is only my second patch ever, I screwed up my first one with bugs, and even though I tested this a lot this time, it wouldn't hurt some more feedback. Patch the svn with http://mega.ist.utl.pt/~nhqb/gentoo/catalyst/catalyst_luks_02.patch Documentation is in the livecd-stage2 example. Use the linuxrc below and choose 'manual' mode ('keyfile' mode requires http://bugs.gentoo.org/show_bug.cgi?id=162962). Hopefully this will be the default genkernel linuxrc. http://mega.ist.utl.pt/~nhqb/gentoo/catalyst/linuxrc Cheers, Nelson -- [EMAIL PROTECTED] mailing list
