Package: git-crypt
Version: 0.5.0-2
Architecture: amd64
Maintainer: Andrew Ayer <agwa@andrewayer.name>
Installed-Size: 224
Depends: libc6 (>= 2.14), libgcc1 (>= 1:4.1.1), libssl1.0.0 (>= 1.0.0), libstdc++6 (>= 4.4.0), git (>= 1.7.2)
Recommends: gnupg
Enhances: git
Filename: ./amd64/git-crypt_0.5.0-2_amd64.deb
Size: 75538
MD5sum: 87ccf6f6a55b5e27e0cb9d7cd27cd99a
SHA1: f9c12c40283826d7de6928d90df95c2730cea981
SHA256: 9ada6f0198bf01fcf232c469c93047d3eef95997b0ebfa5aa6e4882c8269782e
Section: vcs
Priority: optional
Homepage: https://www.agwa.name/projects/git-crypt
Description: Transparent file encryption in git
 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 repository with encrypted files.
 This lets you store your secret material (such as keys or passwords)
 in the same repository as your code, without requiring you to lock down
 your entire repository.

Package: git-crypt
Version: 0.5.0-2
Architecture: i386
Maintainer: Andrew Ayer <agwa@andrewayer.name>
Installed-Size: 215
Depends: libc6 (>= 2.4), libgcc1 (>= 1:4.1.1), libssl1.0.0 (>= 1.0.0), libstdc++6 (>= 4.4.0), git (>= 1.7.2)
Recommends: gnupg
Enhances: git
Filename: ./i386/git-crypt_0.5.0-2_i386.deb
Size: 75858
MD5sum: cfc6c24e17dc6fdc4736f1e012e7afe6
SHA1: fa41efc1c67778891a46b4fb57a3cf495b4546e3
SHA256: bdb8afb4fb30ef47104962948d4f49cd59ca53b75887fbfad1b6bce7b9c2df46
Section: vcs
Priority: optional
Homepage: https://www.agwa.name/projects/git-crypt
Description: Transparent file encryption in git
 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 repository with encrypted files.
 This lets you store your secret material (such as keys or passwords)
 in the same repository as your code, without requiring you to lock down
 your entire repository.