diff options
author | Rafael J. Wysocki <rjw@sisk.pl> | 2011-03-04 00:25:23 +0100 |
---|---|---|
committer | Rafael J. Wysocki <rafael@ferrari.rjw.lan> | 2011-03-04 00:25:23 +0100 |
commit | 1586daf42060f9f347e9a935fa78f360c4cb1a93 (patch) | |
tree | 465d1ffe58dc8c8503a708b7ac5a62382e4f4014 | |
parent | b8ff27ee9530be07ad19e15b82dd05d1159e2ba5 (diff) | |
download | suspend-utils-1586daf42060f9f347e9a935fa78f360c4cb1a93.tar.gz |
s2disk: Update encryption documentation
Remove a reference to suspend.sf.net from README.encryption and
polish the wording in that file a bit.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
-rw-r--r-- | README.encryption | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/README.encryption b/README.encryption index a5957fa..3cdf999 100644 --- a/README.encryption +++ b/README.encryption @@ -1,11 +1,11 @@ Suspend encryption ~~~~~~~~~~~~~~~~~~ -Encryption in suspend.sf.net uses RSA internally; reason is that we -want to only prompt for passphrase on resume. So, during suspend, -image is effectively encrypted with public key, and during resume, -user has to first decrypt private key using passphrase, which then -decrypts the image. +Encryption in suspend-utils uses RSA internally; the reason is that we +want to only prompt for passphrase on resume. So, during suspend, the +image is effectively encrypted with a public key, and during resume, +the user has to first decrypt the corresponding private key using a +passphrase, which then is used to decrypt the image. The image is always encrypted with symmetric algo. If RSA is used (optional) then the key for the symmetric encryption is random and the |