comment
authorJoey Hess <joeyh@joeyh.name>
Sat, 19 Dec 2015 18:07:57 +0000 (14:07 -0400)
committerJoey Hess <joeyh@joeyh.name>
Sat, 19 Dec 2015 18:07:57 +0000 (14:07 -0400)
doc/forum/Future_proofing___47___disaster_recovery_with_an_encrypted_special_remote/comment_5_5aecb8c58d501e929e746d5536032c81._comment [new file with mode: 0644]

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 (file)
index 0000000..8c3478d
--- /dev/null
@@ -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.
+"""]]