diff options
| -rw-r--r-- | doc/forum/Future_proofing___47___disaster_recovery_with_an_encrypted_special_remote/comment_5_5aecb8c58d501e929e746d5536032c81._comment | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/doc/forum/Future_proofing___47___disaster_recovery_with_an_encrypted_special_remote/comment_5_5aecb8c58d501e929e746d5536032c81._comment b/doc/forum/Future_proofing___47___disaster_recovery_with_an_encrypted_special_remote/comment_5_5aecb8c58d501e929e746d5536032c81._comment new file mode 100644 index 000000000..8c3478d97 --- /dev/null +++ b/doc/forum/Future_proofing___47___disaster_recovery_with_an_encrypted_special_remote/comment_5_5aecb8c58d501e929e746d5536032c81._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 5""" + date="2015-12-19T17:59:38Z" + content=""" +When using `pubkey`, the second 256 bytes of ciphertext are currently +not used for anything. + +For `hybrid` and `shared`, the 256 bytes of ciphertext are used +as a symmetric cipher. So the gpg option to use for both encrypting +and decrypting is --symmetric. gpg then prompts for a passphrase, +and the ciphertext is what's used. +"""]] |