transcrypt v2.2.0

This release includes compatibility with OpenSSL 3, installs a single script into the Git crypt/ directory instead of multiple, adds the option --set-openssl-path to use a specific version of openssl, and a number of other tweaks and fixes.

Steps to upgrade

1. Make sure you are running the latest version of transcrypt:

   $ transcrypt --version
   

2. Upgrade a repository:

   $ transcrypt --upgrade
   

Feature summary

Added

• Add --set-openssl-path option to configure transcrypt to use a specific openssl version instead of the default version found in $PATH. This will be most useful to macOS users who might want to use a newer version of OpenSSL. This option can be used on init, on upgrade, or by itself.
• Add support for an optional transcrypt.crypt-dir setting for advanced users to override the path of the .git/crypt/ directory to permit things like installing transcrypt in a repository on a device without execute permissions (#104)

Changed

• No longer need stand-alone scripts for git operations clean, smudge, textconv, and merge in the repository's crypt/ directory; the single consolidated transcrypt script is stored there instead.

Fixed

• Remain compatible with OpenSSL versions 3 and above which changes the way explicit salt values are expressed in ciphertext, requires xxd command (#133)
• Ensure Git index is up-to-date before checking for dirty repo, to avoid failures seen in CI systems where the repo seems dirty when it isn't. (#37)
• Respect Git core.hooksPath setting when installing the pre-commit hook. (#104)
• Zsh completion. (#107)
• Fix salt generation for partial (patch) commits (#118)
• Improve command hint to fix secret files not encrypted in index (#120)
• Fix handling of files with null in first 8 bytes (#116)