mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

removed

Browse source
This commit is contained in:
joern.mankiewicz@06fb5bc9b732f143dee3606866362f562531310d 2017-03-21 22:08:52 +00:00 • committed by admin
parent 877d42fe77
commit 02b61aee9a
1 changed files with 0 additions and 20 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

20
doc/encryption/comment_7_60b251fea4b4c84e31ec0cd69779aec8._comment
View file

@ -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
"""]]