Added a comment: Workflow for adding a keyid in hybrid-enc lateron and re-encrypting?

1 files changed, 20 insertions, 0 deletions

diff --git a/doc/encryption/comment_8_3849eb24c3682644e263bae107747dee._comment b/doc/encryption/comment_8_3849eb24c3682644e263bae107747dee._comment
new file mode 100644
index 000000000..393d18ecc
--- /dev/null
+++ b/doc/encryption/comment_8_3849eb24c3682644e263bae107747dee._comment
@@ -0,0 +1,20 @@
+[[!comment format=mdwn
+ username="joern.mankiewicz@06fb5bc9b732f143dee3606866362f562531310d"
+ nickname="joern.mankiewicz"
+ avatar="http://cdn.libravatar.org/avatar/446365f4d50dddc42965fa0432e70cdb"
+ subject="Workflow for adding a keyid in hybrid-enc lateron and re-encrypting? "
+ date="2017-03-21T22:08:30Z"
+ content="""
+Hi folks!
+
+We are considering introducing git-annex with gcrypt in hybrid mode as secure storage for common data in our company and I'd rather not delete and reinit the repo everytime when somebody new is granted access.
+A little testing with current git-annex showed, that GCRYPT_FULL_REPACK with a forced git-push of all branches makes the git-repo accessible (I get the files) to the newcomer but not the annexed data (gpg error \"No secret key\" in git annex get, git annex info secretRepo just lists my first key).
+
+Has anybody sucessfully tested adding keyids in hybrid-encryption later on? Which further steps where needed to make it work? 
+
+Thanks for any input! :)
+
+Cheers 
+
+Jörn
+"""]]