summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar joern.mankiewicz@06fb5bc9b732f143dee3606866362f562531310d <joernmankiewicz@web>2017-03-21 22:08:52 +0000
committerGravatar admin <admin@branchable.com>2017-03-21 22:08:52 +0000
commit93b7cceb0f193b8a5d44ffc42ecbb858efbec3f6 (patch)
tree1ad17926660565136ae7db89ba7d76c278095862
parentabcbccdd5e7a1df89be05880039e4a0481b76172 (diff)
removed
-rw-r--r--doc/encryption/comment_7_60b251fea4b4c84e31ec0cd69779aec8._comment20
1 files changed, 0 insertions, 20 deletions
diff --git a/doc/encryption/comment_7_60b251fea4b4c84e31ec0cd69779aec8._comment b/doc/encryption/comment_7_60b251fea4b4c84e31ec0cd69779aec8._comment
deleted file mode 100644
index f5286b43e..000000000
--- a/doc/encryption/comment_7_60b251fea4b4c84e31ec0cd69779aec8._comment
+++ /dev/null
@@ -1,20 +0,0 @@
-[[!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:22Z"
- 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
-"""]]