Git-crypt — git-crypt enables transparent encryption and decryption of files in a git repository. Files which you choose to protect are encrypted when committed, and decrypted when checked out. Git-crypt lets you freely share a repository containing a mix of public and private content. Git-crypt gracefully degrades, so developers without the secret key can still clone and commit to a.
Download the bundle AGWA-git-crypt_-_2017-05-20_12-04-26.bundle and run:Transparent file encryption in git
git-crypt enables transparent encryption and decryption of files in agit repository. Files which you choose to protect are encrypted whencommitted, and decrypted when checked out. git-crypt lets you freelyshare a repository containing a mix of public and private content.git-crypt gracefully degrades, so developers without the secret key canstill clone and commit to a repository with encrypted files. This letsyou store your secret material (such as keys or passwords) in the samerepository as your code, without requiring you to lock down your entirerepository.
git-crypt was written by Andrew Ayer (agwa@andrewayer.name).For more information, see https://www.agwa.name/projects/git-crypt.
Building git-crypt
See the INSTALL.md file.
Using git-crypt
Configure a repository to use git-crypt:
Specify files to encrypt by creating a .gitattributes file:
Like a .gitignore file, it can match wildcards and should be checked intothe repository. See below for more information about .gitattributes.Make sure you don't accidentally encrypt the .gitattributes file itself(or other git files like .gitignore or .gitmodules). Make sure your.gitattributes rules are in place before you add sensitive files, orthose files won't be encrypted!
Share the repository with others (or with yourself) using GPG:
USER_ID can be a key ID, a full fingerprint, an email address, oranything else that uniquely identifies a public key to GPG (see 'HOW TOSPECIFY A USER ID' in the gpg man page). Note: git-crypt add-gpg-userwill add and commit a GPG-encrypted key file in the .git-crypt directoryof the root of your repository.
Alternatively, you can export a symmetric secret key, which you mustsecurely convey to collaborators (GPG is not required, and no filesare added to your repository):
After cloning a repository with encrypted files, unlock with with GPG:
Or with a symmetric key:
That's all you need to do - after git-crypt is set up (either withgit-crypt init or git-crypt unlock), you can use git normally -encryption and decryption happen transparently.
Current Status
The latest version of git-crypt is 0.5.0, released on2015-05-30. git-crypt aims to be bug-free and reliable, meaning itshouldn't crash, malfunction, or expose your confidential data.However, it has not yet reached maturity, meaning it is not asdocumented, featureful, or easy-to-use as it should be. Additionally,there may be backwards-incompatible changes introduced before version1.0.
Security
git-crypt is more secure that other transparent git encryption systems.git-crypt encrypts files using AES-256 in CTR mode with a synthetic IVderived from the SHA-1 HMAC of the file. This mode of operation isprovably semantically secure under deterministic chosen-plaintext attack.That means that although the encryption is deterministic (which isrequired so git can distinguish when a file has and hasn't changed),it leaks no information beyond whether two files are identical or not.Other proposals for transparent git encryption use ECB or CBC with afixed IV. These systems are not semantically secure and leak information.
Limitations
git-crypt relies on git filters, which were not designed with encryptionin mind. As such, git-crypt is not the best tool for encrypting most orall of the files in a repository. Where git-crypt really shines is wheremost of your repository is public, but you have a few files (perhapsprivate keys named *.key, or a file with API credentials) which youneed to encrypt. For encrypting an entire repository, consider using asystem like git-remote-gcryptinstead. (Note: no endorsement is made of git-remote-gcrypt's security.)
git-crypt does not encrypt file names, commit messages, symlink targets,gitlinks, or other metadata.
git-crypt does not hide when a file does or doesn't change, the lengthof a file, or the fact that two files are identical (see 'Security'section above).
Files encrypted with git-crypt are not compressible. Even the smallestchange to an encrypted file requires git to store the entire changed file,instead of just a delta.
Although git-crypt protects individual file contents with a SHA-1HMAC, git-crypt cannot be used securely unless the entire repository isprotected against tampering (an attacker who can mutate your repositorycan alter your .gitattributes file to disable encryption). If necessary,use git features such as signed tags instead of relying solely ongit-crypt for integrity.
Files encrypted with git-crypt cannot be patched with git-apply, unlessthe patch itself is encrypted. To generate an encrypted patch, use gitdiff --no-textconv --binary. Alternatively, you can apply a plaintextpatch outside of git using the patch command.
git-crypt does not work reliably with some third-party git GUIs, suchas Atlassian SourceTreeand GitHub for Mac. Files might be left in an unencrypted state.
Gitattributes File
The .gitattributes file is documented in the gitattributes(5) man page.The file pattern format is the same as the one used by .gitignore,as documented in the gitignore(5) man page, with the exception thatspecifying merely a directory (e.g. /dir/) is not sufficient toencrypt all files beneath it.
Also note that the pattern dir/* does not match files undersub-directories of dir/. To encrypt an entire sub-tree dir/, place thefollowing in dir/.gitattributes:
The second pattern is essential for ensuring that .gitattributes itselfis not encrypted.
Mailing Lists
To stay abreast of, and provide input to, git-crypt development,consider subscribing to one or both of our mailing lists:
Asymmetric Key
Source: https://github.com/AGWA/git-cryptSymmetric Key Cryptography
Uploader: AGWA