From ca44869f59cf568b499c119ee2578fc920bde6cf Mon Sep 17 00:00:00 2001
From: "http://phil.0x539.de/" <Philipp_Kern@web>
Date: Thu, 7 Mar 2013 15:21:55 +0000
Subject: Added a comment

---
 .../comment_7_c1eb59e1c5f583dcef7cea17623a2435._comment           | 8 ++++++++
 1 file changed, 8 insertions(+)
 create mode 100644 doc/bugs/encryption_key_is_surprising/comment_7_c1eb59e1c5f583dcef7cea17623a2435._comment

(limited to 'doc')

diff --git a/doc/bugs/encryption_key_is_surprising/comment_7_c1eb59e1c5f583dcef7cea17623a2435._comment b/doc/bugs/encryption_key_is_surprising/comment_7_c1eb59e1c5f583dcef7cea17623a2435._comment
new file mode 100644
index 000000000..ac8ac31df
--- /dev/null
+++ b/doc/bugs/encryption_key_is_surprising/comment_7_c1eb59e1c5f583dcef7cea17623a2435._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="http://phil.0x539.de/"
+ nickname="Philipp Kern"
+ subject="comment 7"
+ date="2013-03-07T15:21:55Z"
+ content="""
+For the default git-annex will pass plenty of key bytes to make this unnecessary. True, one could adjust <code>$HOME/.gnupg/gpg.conf</code> to select another s2k algorithm and another cipher for the data (the two relevant options being <code>s2k-digest-algo</code> and <code>cipher-algo</code>. To be honest, I'd also like a per-repository gpg options setting for the symmetric cipher. For instance I know that I always want compression with gpg unless I use it with annexed data (at least in certain repositories).
+"""]]
-- 
cgit v1.2.3