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

Merge branch 'master' of ssh://git-annex.branchable.com

Browse source
This commit is contained in:
Joey Hess 2013-08-22 13:57:38 -04:00
commit 96fc3a63ac
3 changed files with 37 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
doc/bugs/Using_a_revoked_GPG_key/comment_8_9dc921dc6077f828454a4444088b9a43._comment Normal file
View file

@ -0,0 +1,15 @@
[[!comment format=mdwn
username="http://joeyh.name/"
ip="4.154.0.63"
subject="comment 8"
date="2013-08-22T17:05:49Z"
content="""
Note that the assistant generates initremote parameters so code there also needs to be changed if the syntax changes.
I think I am ok with changing the syntax. However, it seems that `encryption=-oldkey encryption=newkey` could be used to remove the old revoked key and add a new one. Using `-keyid` as a parameter to initremote is a bit tricky since git-annex's regular option parser would see it, before the parameter could get to initremote. (Unless -keyid was defined as a regular option specific to initremote.) OR, git-annex could just try to detect when a key is revoked and automatically remove it when a new encryption key is specified.
Hmm, it would be possible to have it just notice, when adding a new key, if one of the existing keys is revoked, and
remove the revoked key automatically.
The above doesn't deal with the case of wanting to add pure asymmetric encryption. It seems to me that from a user's point of view, what they really need to know about asymmetric encryption is that they can't easily give additional keyids access after the fact (without reencrypting and reuploading everything). So I think it would be good if the syntax made that obvious. Perhaps `encryptiononly=key`
"""]]

10
doc/bugs/non-annexed_file_changed_to_annexed_on_typechange/comment_8_c53ce2274388711ffbde1595b64f932b._comment Normal file
View file

@ -0,0 +1,10 @@
[[!comment format=mdwn
username="http://joeyh.name/"
ip="4.154.0.63"
subject="comment 8"
date="2013-08-22T17:25:48Z"
content="""
Yay for the git-annex community for another fine bug testcase!
The problem is simply that it assumes any typechanged link was an annexed file, and doesn't doublecheck. Fixing that now..
"""]]

12
doc/todo/wishlist:_perform_fsck_remotely/comment_2_2f0dbaf143d94290bfbebb6869eb7241._comment Normal file
View file

@ -0,0 +1,12 @@
[[!comment format=mdwn
username="guilhem"
ip="129.16.20.209"
subject="comment 2"
date="2013-08-22T16:56:55Z"
content="""
Oh yeah, the MDC paragraph was pretty much pointless indeed. Oops :-P
I agree that this would potentially add some noise to the index, and weaken the
security, but depending on the threat model and people's preferences that's an
option that's worth considering IMHO.
"""]]