On Thu, Apr 14, 2005 at 12:29:36AM +0200, Andreas Steinmetz wrote: > > > Why is that? In the case of swap over dmcrypt, swsusp never reads/writes > > the disk directly. All operations are done through dmcrypt. > > > > The user has to enter a password before the system can be resumed. > > Think of it the following way: user suspend and later resumes. During > suspend some mlocked memory e.g. from ssh-agent gets dumped to swap. > Some days later the system gets broken in from a remote place. > Unfortunately the ssh keys are still on swap (assuming that ssh-agent is > not running then) and can be recovered by the intruder. The intruder can
The ssh keys are *encrypted* in the swap when dmcrypt is used. When the swap runs over dmcrypt all writes including those from swsusp are encrypted. Cheers, -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
