diff options
author | Joey Hess <joey@kitenet.net> | 2013-09-04 18:15:38 -0400 |
---|---|---|
committer | Joey Hess <joey@kitenet.net> | 2013-09-04 18:15:38 -0400 |
commit | 96440fd14b932783d268477f45e9540237b56f21 (patch) | |
tree | d62ab9651723b87bfc008b6e68db387d0f9c5e40 /debian | |
parent | 02b51c10f48e9205d2a18d58430143be6f3ae78e (diff) |
detailed changelog for the encryption changes
Diffstat (limited to 'debian')
-rw-r--r-- | debian/changelog | 17 |
1 files changed, 17 insertions, 0 deletions
diff --git a/debian/changelog b/debian/changelog index f880fbcf7..fb24feabe 100644 --- a/debian/changelog +++ b/debian/changelog @@ -11,6 +11,23 @@ git-annex (4.20130828) UNRELEASED; urgency=low from feeds. * Honor core.sharedrepository when receiving and adding files in direct mode. + * enableremote: gpg keys can be removed from those a remote encrypts + to by passing "keyid-=$KEYID". keyid+= is also provided, although + "encryption=$KEYID" can also be used as always. + (Thanks, guilhem for the patch.) + * initremote: A new encryption scheme can be selected with + "encryption=pubkey keyid=$KEYID" + This causes files placed on special remotes to be directly + encrypted to the specified key(s). It is not possible to add + other keys later and have them immedately be able to access those + encrypted files, like can be done with the default encryption scheme. + However, pubkey encryption may be considered more secure due to being + and more standard use of gpg that avoids symmetric encryption algorythms, + or just simpler if you're the only person you ever intend to use a + particular encrypted special remote. + (Thanks, guilhem for the patch.) + + -- Joey Hess <joeyh@debian.org> Tue, 27 Aug 2013 11:03:00 -0400 git-annex (4.20130827) unstable; urgency=low |