aboutsummaryrefslogtreecommitdiff
path: root/development/git-crypt/README
diff options
context:
space:
mode:
authorNicolas Piatto <nico@lodpp.net>2021-03-05 22:57:13 +0000
committerWilly Sudiarto Raharjo <willysr@slackbuilds.org>2021-03-06 11:11:53 +0700
commit8805058fdfed520b8494f3fc9c1ffb6670bb889b (patch)
tree00d06ad9f0edd2d7f676268bf63956d9093c269e /development/git-crypt/README
parentc399dd335d5adda2111b54ef2418606789adbba3 (diff)
development/git-crypt: Added (transparent file encryption in git)
Signed-off-by: Dave Woodfall <dave@slackbuilds.org> Signed-off-by: Willy Sudiarto Raharjo <willysr@slackbuilds.org>
Diffstat (limited to 'development/git-crypt/README')
-rw-r--r--development/git-crypt/README11
1 files changed, 11 insertions, 0 deletions
diff --git a/development/git-crypt/README b/development/git-crypt/README
new file mode 100644
index 0000000000..6363c7b888
--- /dev/null
+++ b/development/git-crypt/README
@@ -0,0 +1,11 @@
+git-crypt - 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.