reword changelog

This commit is contained in:
Joey Hess 2013-09-04 19:31:36 -04:00
parent b17defd43a
commit 6e09893160

16
debian/changelog vendored
View file

@ -11,20 +11,16 @@ git-annex (4.20130828) UNRELEASED; urgency=low
from feeds. from feeds.
* Honor core.sharedrepository when receiving and adding files in direct * Honor core.sharedrepository when receiving and adding files in direct
mode. mode.
* initremote: Syntax change when setting up encrypted special remote.
Now use: encryption=hybrid keyid=$KEYID
(Thanks, guilhem for the patch.)
* enableremote: gpg keys can be removed from those a remote encrypts * enableremote: gpg keys can be removed from those a remote encrypts
to by passing "keyid-=$KEYID". keyid+= is also provided, although to by passing "keyid-=$KEYID". keyid+= is also provided, although
"encryption=$KEYID" can also be used as always. "encryption=$KEYID" can also be used as always.
(Thanks, guilhem for the patch.) (Thanks, guilhem for the patch.)
* initremote: A new encryption scheme can be selected with * Added encryption=pubkey scheme, which encrypts to public keys directly
"encryption=pubkey keyid=$KEYID" rather than the hybrid approach. See documentation for advantages
This causes files placed on special remotes to be directly and disadvantages, but encryption=hybrid is the recommended scheme still.
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.) (Thanks, guilhem for the patch.)
-- Joey Hess <joeyh@debian.org> Tue, 27 Aug 2013 11:03:00 -0400 -- Joey Hess <joeyh@debian.org> Tue, 27 Aug 2013 11:03:00 -0400