Package: git-crypt
Version: 0.5.0-2
Architecture: i386
Maintainer: Andrew Ayer <agwa@andrewayer.name>
Installed-Size: 190
Depends: libc6 (>= 2.4), libgcc1 (>= 1:3.0), libssl1.0.0 (>= 1.0.0), libstdc++6 (>= 5.2), git (>= 1.7.2)
Recommends: gnupg
Enhances: git
Filename: ./i386/git-crypt_0.5.0-2_i386.deb
Size: 76024
MD5sum: 4da469205d4f51d69eff8c9537a12576
SHA1: 2c32fd9e99f33060445533879768ab3fc32355df
SHA256: 3db44ea5ddd3b181e1a015e9b75d9aa7919cd5ef39b298972ca2fc0849d89efc
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: amd64
Maintainer: Andrew Ayer <agwa@andrewayer.name>
Installed-Size: 196
Depends: libc6 (>= 2.14), libgcc1 (>= 1:3.0), libssl1.0.0 (>= 1.0.0), libstdc++6 (>= 5.2), git (>= 1.7.2)
Recommends: gnupg
Enhances: git
Filename: ./amd64/git-crypt_0.5.0-2_amd64.deb
Size: 74076
MD5sum: b9c95db581400ec3fabe2edc9f89d7b4
SHA1: 33083807b9e2a8e0704624f0ac28da32b5042d3c
SHA256: 3bbe886b32ed13a4ba5d546517c6afc0ca82325ecc3069d1d3ed196253b0d012
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.