public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Wainwright <prw@ceiriog.eclipse.co.uk>
To: Pavel Machek <pavel@ucw.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Announcing crypto suspend
Date: Mon, 20 Mar 2006 18:35:05 +0000	[thread overview]
Message-ID: <1142879707.9475.4.camel@localhost.localdomain> (raw)
In-Reply-To: <20060320080439.GA4653@elf.ucw.cz>

On Mon, 2006-03-20 at 09:04 +0100, Pavel Machek wrote:
> Hi!
> 
> Thanks to Rafael's great work, we now have working encrypted suspend
> and resume. You'll need recent -mm kernel, and code from
> suspend.sf.net. Due to its use of RSA, you'll only need to enter
> password during resume.
> 
> [Code got some minimal review; if you are a crypto expert, and think
> you can poke a hole within it, please try to do so.]
> 								Pavel
Thats pretty interesting - we really need a featureful suspend
implementation
in mainline. But there doesn't seem to be much documentation for it.
suspend.sf.net takes me to the Suspend 2 site: www.suspend2.net (a
virtual
server?). Which code from this site is needed for the mainline suspend?

Peter



  parent reply	other threads:[~2006-03-20 18:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-20  8:04 Announcing crypto suspend Pavel Machek
2006-03-20 14:13 ` Andreas Jellinghaus
2006-03-20 18:35 ` Peter Wainwright [this message]
2006-03-20 18:44   ` Pavel Machek
2006-03-20 19:26     ` Peter Wainwright
2006-03-20 18:54   ` Rafael J. Wysocki
2006-03-20 19:11     ` Alon Bar-Lev
2006-03-20 20:26       ` Rafael J. Wysocki
2006-03-20 20:35         ` Pavel Machek
2006-03-20 21:22           ` Rafael J. Wysocki
2006-03-20 21:34             ` Pavel Machek
2006-03-20 22:05               ` Alon Bar-Lev
2006-03-20 22:18                 ` Pavel Machek
2006-03-20 22:24                 ` Andreas Happe
2006-03-21  9:45     ` Andreas Jellinghaus
2006-03-21 20:50       ` Pavel Machek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1142879707.9475.4.camel@localhost.localdomain \
    --to=prw@ceiriog.eclipse.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox