Skip to content

Latest commit

 

History

History
73 lines (65 loc) · 3.33 KB

NEWS.md

File metadata and controls

73 lines (65 loc) · 3.33 KB
Raw

News

######v0.6.0 (2017-11-26)

  • Add support for OpenSSL 1.1 (still works with OpenSSL 1.0).
  • Switch to C++11 (gcc 4.9 or higher now required to build).
  • Allow GPG to fail on some keys (makes unlock work better if there are multiple keys that can unlock the repo but only some are available).
  • Allow the repo state directory to be configured with the git-crypt.repoStateDir git config option.
  • Respect the gpg.program git config option.
  • Don't hard code path to git-crypt in .git/config on Linux (ensures repo continues to work if git-crypt is moved).
  • Ensure git-crypt's gpg files won't be treated as text by Git.
  • Minor improvements to build system, documentation.

######v0.5.0 (2015-05-30)

  • Drastically speed up lock/unlock when used with Git 1.8.5 or newer.
  • Add git-crypt(1) man page (pass ENABLE_MAN=yes to make to build).
  • Add --trusted option to git-crypt gpg-add-user to add user even if GPG doesn't trust user's key.
  • Improve git-crypt lock usability, add --force option.
  • Ignore symlinks and other non-files when running git-crypt status.
  • Fix compilation on old versions of Mac OS X.
  • Fix GPG mode when with-fingerprint enabled in gpg.conf.
  • Minor bug fixes and improvements to help/error messages.

######v0.4.2 (2015-01-31)

  • Fix unlock and lock under Git 2.2.2 and higher.
  • Drop support for versions of Git older than 1.7.2.
  • Minor improvements to some help/error messages.

######v0.4.1 (2015-01-08)

  • Important usability fix to ensure that the .git-crypt directory can't be encrypted by accident (see the release notes for more information).

######v0.4 (2014-11-16) (See the release notes for important details.)

  • Add optional GPG support: GPG can be used to share the repository between one or more users in lieu of sharing a secret key.
  • New workflow: the symmetric key is now stored inside the .git directory. Although backwards compatibility has been preserved with repositories created by old versions of git-crypt, the commands for setting up a repository have changed. See the release notes file for details.
  • Multiple key support: it's now possible to encrypt different parts of a repository with different keys.
  • Initial git-crypt status command to report which files are encrypted and to fix problems that are detected.
  • Numerous usability, documentation, and error reporting improvements.
  • Major internal code improvements that will make future development easier.
  • Initial experimental Windows support.

######v0.3 (2013-04-05)

  • Fix git-crypt init on newer versions of Git. Previously, encrypted files were not being automatically decrypted after running git-crypt init with recent versions of Git.
  • Allow git-crypt init to be run even if the working tree contains untracked files.
  • git-crypt init now properly escapes arguments to the filter commands it configures, allowing both the path to git-crypt and the path to the key file to contain arbitrary characters such as spaces.

######v0.2 (2013-01-25)

  • Numerous improvements to git-crypt init usability.
  • Fix gitattributes example in README: the old example showed a colon after the filename where there shouldn't be one.
  • Various build fixes and improvements.

######v0.1 (2012-11-29)

  • Initial release.