From fe0a56c1222e64c32a324597797bd319efa75c8a Mon Sep 17 00:00:00 2001 From: Philipp Kern Date: Thu, 7 Mar 2013 16:24:06 +0100 Subject: bugs/encryption_key_is_surprising/comment_7: add a closing brace --- .../comment_7_c1eb59e1c5f583dcef7cea17623a2435._comment | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'doc/bugs/encryption_key_is_surprising') diff --git a/doc/bugs/encryption_key_is_surprising/comment_7_c1eb59e1c5f583dcef7cea17623a2435._comment b/doc/bugs/encryption_key_is_surprising/comment_7_c1eb59e1c5f583dcef7cea17623a2435._comment index ac8ac31df..19863e8f8 100644 --- a/doc/bugs/encryption_key_is_surprising/comment_7_c1eb59e1c5f583dcef7cea17623a2435._comment +++ b/doc/bugs/encryption_key_is_surprising/comment_7_c1eb59e1c5f583dcef7cea17623a2435._comment @@ -4,5 +4,5 @@ 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 $HOME/.gnupg/gpg.conf to select another s2k algorithm and another cipher for the data (the two relevant options being s2k-digest-algo and cipher-algo. 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). +For the default git-annex will pass plenty of key bytes to make this unnecessary. True, one could adjust $HOME/.gnupg/gpg.conf to select another s2k algorithm and another cipher for the data (the two relevant options being s2k-digest-algo and cipher-algo). 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