Package: git-crypt
Version: 0.5.0-2
Architecture: i386
Maintainer: Andrew Ayer <agwa@andrewayer.name>
Installed-Size: 207
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: 86908
MD5sum: a043b9e61e3484898ca2dd4f8215c4f3
SHA1: 0a299e2562e5249a2f47c93436730c55cdcf0a87
SHA256: 57b0b79d09bfd2d57ab7f21f83336943464d5e6d90652d90701021e4bb146f20
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: 216
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: 87416
MD5sum: 614e7d4face4a7487bd4210ef0b714fd
SHA1: 195156d7f0167a7c3e456ae676311f4c66ceb290
SHA256: 876a6f1a9d6f816a846fc39976dad393abd88e44a182a15fb04799eef491f163
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.